azurerm_key_vault_access_policy - check access policy consistency before committing to state
#9125
Conversation
azurerm/internal/services/keyvault/key_vault_access_policy_resource.go
Outdated
Show resolved
Hide resolved
|
|
||
| if _, err := stateConf.WaitForState(); err != nil { | ||
| return fmt.Errorf("failed waiting for Key Vault Access Policy (Object ID: %q) to apply: %+v", objectId, err) | ||
| } |
There was a problem hiding this comment.
(as discussed offline) this likely wants adding to the key vault resource's update function, too - to ensure that's covered from this edge-case too?
jackofallops
force-pushed
the
b/keyvault-permissions
branch
from
c8115ef
to
3634fb7
Compare
|
Tests passing: |
|
This has been released in version 2.35.0 of the provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. As an example: provider "azurerm" {
version = "~> 2.35.0"
}
# ... other configuration ... |
…ged into azurerm 2.35.0
…ged into azurerm 2.35.0
…ged into azurerm 2.35.0
…ged into azurerm 2.35.0 (#893)
…ged into azurerm 2.35.0 (#893)
…ged into azurerm 2.35.0 (#893)
…ged into azurerm 2.35.0 (#893)
…ged into azurerm 2.35.0 (#893)
…ged into azurerm 2.35.0 (#893)
|
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 👉 hashibot-feedback@hashicorp.com. Thanks! |
ghost
locked as resolved and limited conversation to collaborators
fixes #9107