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
Vault Name: "rsv-backup-test"): performing CreateOrUpdate: unexpected status 400 with error: UserErrorUnsupportedVaultImmutabilityStateChange: The immutable vault property for this vault is locked, hence, this setting cannot be disabled. The vault has its immutable vault property enabled and locked, and it can no longer be reverted to a non-immutable vault. Refer to the documentation to learn more: https://aka.ms/AB-ImmutableVaults-States
Expected Behaviour
Recovery Vault is created
Actual Behaviour
No vault is created and error is thrown
Steps to Reproduce
terraform init
terraform apply
It is not a terraform issue but one of the Azure CLI. It can also be reproduced running the command: az backup vault create --location eastus --name rsv-backup-test --resource-group rg-backup-test --immutability-state Locked
The workaround is to create the vault first unlocked and then reapply the configuration with the vault locked. Documenting here so it can be linked to a Microsoft API issue, thank
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered:
per tesing, the immutability can not be directly set to Locked from Disabled, and it acts as same as Portal, which I personally assume it's by design. I have submiteed a PR to let terraform manage this correctly (#23806). Once it merged it should work fine.
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.
Is there an existing issue for this?
Community Note
Terraform Version
1.5.7
AzureRM Provider Version
3.77
Affected Resource(s)/Data Source(s)
azurerm_recovery_services_vault
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
Recovery Vault is created
Actual Behaviour
No vault is created and error is thrown
Steps to Reproduce
terraform init
terraform apply
It is not a terraform issue but one of the Azure CLI. It can also be reproduced running the command:
az backup vault create --location eastus --name rsv-backup-test --resource-group rg-backup-test --immutability-state Locked
The workaround is to create the vault first unlocked and then reapply the configuration with the vault locked. Documenting here so it can be linked to a Microsoft API issue, thank
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: