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
Currently, you cannot specify storage permissions on a keyvault, only key, secret, and certificate.
When creating a new key vault through the az command line utility, the key vault is created with storage permissions. However, when using terraform, there is no way to specify these permissions (as you can with keys, certificates, and secrets). In addition, the provider doesn't generate them by default, so the user or service principal used to create the storage account won't have these permissions either.
This is frequently used when allowing a key vault to manage storage account access keys.
The az script and output. You can see the 'storage section under accessPolicies.
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!
ghost
locked and limited conversation to collaborators
Apr 27, 2019
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Community Note
Description
Currently, you cannot specify storage permissions on a keyvault, only key, secret, and certificate.
When creating a new key vault through the
az
command line utility, the key vault is created with storage permissions. However, when using terraform, there is no way to specify these permissions (as you can with keys, certificates, and secrets). In addition, the provider doesn't generate them by default, so the user or service principal used to create the storage account won't have these permissions either.This is frequently used when allowing a key vault to manage storage account access keys.
The
az
script and output. You can see the 'storage section under accessPolicies.New or Affected Resource(s)
azurerm_key_vault
Potential Terraform Configuration
References
https://docs.microsoft.com/en-us/azure/key-vault/key-vault-ovw-storage-keys#step-by-step-instructions-on-how-to-use-key-vault-to-manage-storage-account-keys
The text was updated successfully, but these errors were encountered: