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
This is part of a larger deployment, and the debug log is > 200k lines.
Panic Output
Expected Behaviour
Actual Behaviour
Key Vault secrets are created in Azure, but the apply session fails. The resources are NOT added to terraform state, so the next run also fails, saying that the resource already exists and needs to be imported.
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.
Community Note
Terraform (and AzureRM Provider) Version
Terraform v1.0.7
azurerm v2.78.0
Affected Resource(s)
azurerm_key_vault_secret
Terraform Configuration Files
Debug Output
This is part of a larger deployment, and the debug log is > 200k lines.
Panic Output
Expected Behaviour
Actual Behaviour
Key Vault secrets are created in Azure, but the apply session fails. The resources are NOT added to terraform state, so the next run also fails, saying that the resource already exists and needs to be imported.
Terraform output first run: https://gist.github.com/tplive/2fa710e2953248abf678178263fef8a1
Terraform output second run: https://gist.github.com/tplive/bf3861a858a073e1f77d0763bb023874
Steps to Reproduce
terraform apply
terraform apply
againImportant Factoids
Key Vault was created earlier, running a pipeline using a different SP.
References
Same issue, closed with azurerm version 2.46:
The text was updated successfully, but these errors were encountered: