Closed nmiodice closed 4 years ago
KV access policies are deleted and re-created after the initial TF apply. Issue Number: https://github.com/microsoft/cobalt/issues/294
KV access policies are created once and need not be updated.
New plan does NOT contain statements about recreating KV access policies. I.E., the following is now omitted from the output of terraform plan
terraform plan
+ resource "azurerm_key_vault_access_policy" "keyvault" { + certificate_permissions = [ + "create", + "delete", + "get", + "list", ] + id = (known after apply) + key_permissions = [ + "create", + "delete", + "get", ] + key_vault_id = "..." + object_id = "..." + resource_group_name = (known after apply) + secret_permissions = [ + "set", + "delete", + "get", + "list", ] + tenant_id = "***" + vault_name = (known after apply) }
Looks good so far. Nice catch on the module usage!
All Submissions:
What is the current behavior?
KV access policies are deleted and re-created after the initial TF apply. Issue Number: https://github.com/microsoft/cobalt/issues/294
What is the new behavior?
KV access policies are created once and need not be updated.
Does this introduce a breaking change?
Any relevant logs, error output, etc?
New plan does NOT contain statements about recreating KV access policies. I.E., the following is now omitted from the output of
terraform plan