-
Notifications
You must be signed in to change notification settings - Fork 21
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
Use azurerm_key_vault_certificate_contacts instead #25
Comments
ah, nvm, this is of course on the consuming-side of things. |
Thanks for this. We will consider the implementation detail. We do not support access policies in the module as yet, preferring Azure role assignments. In your use case, how would the above affect the use of the dedicated contact resource? |
you get a permission denied because the IAM has not been assigned yet - so instead you do this sequence:
|
Thanks. Will swap it out and make dependent on the role assignments |
could this be merged and released? |
Hi, I've put this in another PR that's challenging at the moment. I can pull it out. |
@matt-FFFFFF fix in #39 |
now fixed by #113 |
See hashicorp/terraform-provider-azurerm#19743 and hashicorp/terraform-provider-azurerm#10256 - it might be more optimal to use
azurerm_key_vault_certificate_contacts
to avoid permission problem when initially creating the KV.The text was updated successfully, but these errors were encountered: