Strongdm

- 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.

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

Breaking Changes

- The type of the `Role.access_rules` field has been changed from a string to a list of dicts 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 list of dicts 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](https://github.com/strongdm/strongdm-sdk-python/wiki/Migrating-from-Role-Grants-to-Access-Rules) or check out the
[examples](https://github.com/strongdm/strongdm-sdk-python-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 supportstrongdm.com to learn more.

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

- Added the MongoShardedCluster resource type, which is available as an opt-in beta.