In #223, we renamed the UserWithAccessKey class to pluralize it and allow for multiple keys at once. The old class name was kept around to allow users to transition to the new multi-key model with only a small config change. This included the addition of a new parameter, enabled_legacy_access_key, which is intended to allow users to keep the old access key around while they transition onto the new model. These features will be released with v0.0.16 when the time comes. In a future version, these transitional tools need to be removed.
In #223, we renamed the
UserWithAccessKeyclass to pluralize it and allow for multiple keys at once. The old class name was kept around to allow users to transition to the new multi-key model with only a small config change. This included the addition of a new parameter,enabled_legacy_access_key, which is intended to allow users to keep the old access key around while they transition onto the new model. These features will be released with v0.0.16 when the time comes. In a future version, these transitional tools need to be removed.