key_vault permissions case sensitive

[mrfreester]

Is there an existing issue for this?

• I have searched the existing issues

Community Note

• 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

Terraform Version

0.13

AzureRM Provider Version

3.1

Affected Resource(s)/Data Source(s)

azurerm_key_vault_access_policy

Terraform Configuration Files

resource "azurerm_key_vault_access_policy" "owner_policy" {
  # not relavent....

  secret_permissions = [
    "backup",  #<--- starting with version 3.0 this complains because it doesn't match case
    "delete",
    "get",
    "list",
    "purge",
    "recover",
    "restore",
    "set"
  ]

Debug Output/Panic Output

Error: expected secret_permissions.0 to be one of [Backup Delete Get List Purge Recover Restore Set], got backup

  on azure-keyvault.tf line 25, in resource "azurerm_key_vault_access_policy" "owner_policy":
  25:     "backup",

Expected Behaviour

Values ingore case and are accepted

Actual Behaviour

When first letter isn't capitalized, expected match fails

Steps to Reproduce

Using the azurerm_key_vault_access_policy resource, use lowercase values for any of the permissions rather than uppercase. When terraform runs using a provider of 3.0 or higher the bug is reproduced.

Important Factoids

No response

References

Issue also discussed here:
https://discuss.hashicorp.com/t/secret-permissions-of-azurerm-becomes-case-sensitive/37536

[tombuildsstuff]

hey @mrfreester

Thanks for opening this issue.

These changes were made as a part of 3.0 (and are now correctly documented against the fields within the azurerm_key_vault and azurerm_key_vault_access_policy resources) - as such you'd need to update your configuration to use the fixed casing here.

Double-checking the upgrade guide it appears that this is missing from the upgrade guide for the azurerm_key_vault resource, as such I'll send a PR for that shortly - but this is included for the azurerm_key_vault_access_policy resource: https://registry.terraform.io/providers/hashicorp/azurerm/latest/docs/guides/3.0-upgrade-guide#resource-azurerm_key_vault_access_policy.

Thanks!

[github-actions]

This functionality has been released in v3.2.0 of the Terraform Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[github-actions]

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.