-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
keyvault: normalizing the casing of the permissions #10593
Conversation
Azure's now returning casing which differs from the SDK - as such we need to normalize these on our side. Fixes #10591
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
Tests look good 👍 |
This has been released in version 2.48.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example: provider "azurerm" {
version = "~> 2.48.0"
}
# ... other configuration ... |
Changed * AZ-458: normalizing the casing of the permissions to comply with provider changes hashicorp/terraform-provider-azurerm#10593
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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks! |
This PR normalizes the casing on the Permissions keys within the
azurerm_key_vault
andazurerm_key_vault_access_policy
resources - due to the casing being returned from the API, and the casing on the Constants in the SDK differing. This also adds a DiffSuppressFunc to the Storage Permissions field - to allow for this to happen without diff's, which can ultimately be removed in 3.0 (across all of these) and made case-sensitive, since we're normalizing these casings on Terraform's side.Fixes #10591