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
* azurerm_key_vault_key.dckey: 1 error(s) occurred:
* azurerm_key_vault_key.dckey: azurerm_key_vault_key.dckey: keyvault.BaseClient#GetKey: Failure sending request: StatusCode=0 -- Original Error: Get https://east2-kv.vault.azure.net/keys/DCKey/?api-version=2016-10-01: dial tcp: lookup east2-kv.vault.azure.net: no such host
Expected Behavior
State should be updated so that the key shows it does not exist. If the Azure Key Vault does not exist, then it should be assumed any key it contained no longer exists as well.
There should be a dependency on checking a Key exists only if the Azure Key Vault still exists.
Actual Behavior
State of the key cannot be found since the Azure Key Vault does not exist. This causes the DNS lookup failure since if the Azure Key Vault does not exist then the DNS name will no longer resolve.
Steps to Reproduce
terraform apply
#0000
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 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 👉 [email protected]. Thanks!
ghost
locked and limited conversation to collaborators
Mar 30, 2020
Terraform Version
Terraform v0.11.7
provider.azurerm v1.5.0
Affected Resource(s)
Terraform Configuration Files
Panic Output
Expected Behavior
State should be updated so that the key shows it does not exist. If the Azure Key Vault does not exist, then it should be assumed any key it contained no longer exists as well.
There should be a dependency on checking a Key exists only if the Azure Key Vault still exists.
Actual Behavior
State of the key cannot be found since the Azure Key Vault does not exist. This causes the DNS lookup failure since if the Azure Key Vault does not exist then the DNS name will no longer resolve.
Steps to Reproduce
terraform apply
The text was updated successfully, but these errors were encountered: