Feature Request: Split key vault access policy

[ghost]

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

Description

Split Azure key vault to separate resource. E.g. azurerm_key_vault_access_policy. I have a user case where a function app is depended on a Key Vault. However, I need to grant key vault access through function managed service identity (currently done through resource template). In this situation, the current key vault config will cause circular dependency.

New or Affected Resource(s)

• azurerm_key_vault
• azurerm_key_vault_access_policy

Potential Terraform Configuration

resource "azurerm_key_vault_access_policy" "test" {
    key_vault_id = ""
    tenant_id = "${local.tenant_id}"
    object_id = "${local.object_id}"

    key_permissions    = []
    secret_permissions = ["get", "list"]
}

[tombuildsstuff]

hey @yzhang-myob

Thanks for opening this feature request :)

Support for splitting this out has been requested previously in #754 which will be fixed by #1149 - as such I'm going to close this issue in favour of #754.

Thanks1

[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.