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
╷
│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to azurerm_key_vault_key.container_reg, provider
│ "provider[\"registry.terraform.io/hashicorp/azurerm\"]" produced an
│ unexpected new value: Root resource was present, but now absent.
│
│ This is a bug in the provider, which should be reported in the provider's│ own issue tracker.╵╷│ Error: Provider produced inconsistent result after apply│ │ When applying changes to azurerm_key_vault_secret.appinsight_id, provider│ "provider[\"registry.terraform.io/hashicorp/azurerm\"]" produced an│ unexpected new value: Root resource was present, but now absent.│ │ This is a bug in the provider, which should be reported in the provider's
│ own issue tracker.
╵
╷
│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to
│ module.web_app_apim.azurerm_key_vault_secret.apim_sub, provider
│ "provider[\"registry.terraform.io/hashicorp/azurerm\"]" produced an
│ unexpected new value: Root resource was present, but now absent.
│
│ This is a bug in the provider, which should be reported in the provider's│ own issue tracker.╵╷│ Error: Provider produced inconsistent result after apply│ │ When applying changes to│ azurerm_key_vault_secret.appinsight_instrument_key, provider│ "provider[\"registry.terraform.io/hashicorp/azurerm\"]" produced an│ unexpected new value: Root resource was present, but now absent.│ │ This is a bug in the provider, which should be reported in the provider's
│ own issue tracker.
╵
╷
│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to azurerm_key_vault_secret.web_app, provider
│ "provider[\"registry.terraform.io/hashicorp/azurerm\"]" produced an
│ unexpected new value: Root resource was present, but now absent.
│
│ This is a bug in the provider, which should be reported in the provider's│ own issue tracker.╵╷│ Error: Provider produced inconsistent result after apply│ │ When applying changes to│ module.web_app_apim.azurerm_key_vault_certificate.apim, provider│ "provider[\"registry.terraform.io/hashicorp/azurerm\"]" produced an│ unexpected new value: Root resource was present, but now absent.│ │ This is a bug in the provider, which should be reported in the provider's
│ own issue tracker.
╵
╷
│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to azurerm_key_vault_certificate.web_app, provider
│ "provider[\"registry.terraform.io/hashicorp/azurerm\"]" produced an
│ unexpected new value: Root resource was present, but now absent.
│
│ This is a bug in the provider, which should be reported in the provider's│ own issue tracker.╵
Expected Behaviour
Expect it to create the certificates, secrets and keys
Actual Behaviour
It did not create the resources in the keyvault
Steps to Reproduce
rerunning the terraform, will prompt that you need to import the resources into the statefile
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered:
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
3.201.18
AzureRM Provider Version
3.12.0
Affected Resource(s)/Data Source(s)
azurerm_key_vault
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
Expect it to create the certificates, secrets and keys
Actual Behaviour
It did not create the resources in the keyvault
Steps to Reproduce
rerunning the terraform, will prompt that you need to import the resources into the statefile
Important Factoids
No response
References
No response
The text was updated successfully, but these errors were encountered: