You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Description
The recently implemented encryption option for Azure Container Registry is currently forcing the user to provide a versioned key from Key Vault for the encryption. If you want to setup automatic key rotation you have to pass in a versionless id. This can be fixed by changing the schema to a NestedItemIdWithOptionalVersion.
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
Community Note
Description
The recently implemented encryption option for Azure Container Registry is currently forcing the user to provide a versioned key from Key Vault for the encryption. If you want to setup automatic key rotation you have to pass in a versionless id. This can be fixed by changing the schema to a NestedItemIdWithOptionalVersion.
New or Affected Resource(s)
Potential Terraform Configuration
References
The text was updated successfully, but these errors were encountered: