v2.6.3 - Add optional `keyType` parameter to Cert Based SSH Server that denotes what type of key to generate for communicating with the server.

• Can be one of: rsa-2048, rsa-4096, ecdsa-256, ecdsa-384, ecdsa-521, ed25519
• Previously these were always generated as rsa-2048

v2.6.1 - Support ECDSA and ED25519 in SSH Public Key Servers

Add optional keyType parameter to Public Key SSH Server that denotes what type of key to use.

• Can be one of: rsa-2048, rsa-4096, ecdsa-256, ecdsa-384, ecdsa-521, ed25519
• Previously these were always generated as rsa-2048

v2.6.0 - Remote Identities

• Add Remote Identity support

v2.5.0 - Add bind interface to resources

• Add bind interface to resources

v2.4.0 - add port override option to SSH resources

go: add port override support for SSH resources

GitOrigin-RevId: bd849465eca61158baeefb432b43b41c85f3ac1c

v2.3.0 - add support for bind interface in resources

 add Bind Interface to go SDK

GitOrigin-RevId: 9715feee87dacdd72f6dc28384fd49596a5bc25a

v2.2.0 - Automatic Sleeps for Rate Limits

• This release primarily causes rate limit errors encountered to trigger a sleep until the client knows it can make calls again without encountering that same rate limit. This feature is enabled by default, but can be disabled on client creation.
• Additionally, the schema field for snowflake is no longer a required field.

v2.1.0 - Add mTLS MySQL Resource Type

• This release adds the mTLS MySQL resource type for connecting to a mysql server configured to require specific tls certificates.

v2.0.0 - Access Rules

Breaking Changes

• The type of the Role.AccessRules field has been changed from a string to a slice of structs to improve the usability of access rules. If you are currently using the string field, you'll need to change your code to specify access rules as a slice of structs rather than a string.

Other Changes

• Role Grants are now deprecated and will be removed in a future release. Use Access Rules instead. See the migration guide or check out the examples.

• Composite Roles and Role Attachments are now deprecated and will be removed in a future release. Instead, use AccountAttachments to assign an Account to multiple Roles.

NOTE: Before you can use access rules and multiple account attachments, your organization must undergo the "Access Overhaul" migration to enable the new UI and a myriad of other features. Contact support@strongdm.com to learn more.

v0.9.40 - Adding Azure Key Vault support

• This adds Azure secret store backed by Azure Key Vault
• Exposes NLA downgrade option allows disabling NLA for authentication for RDP servers