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 Response for https://management.azure.com/subscriptions/xyz/providers/Microsoft.KeyVault/vaults?%24skiptoken=%token%&api-version=2023-02-01:
...
Unable to determine the Resource ID for the Key Vault at URL "https://redacted.vault.azure.net/" - removing from state!: timestamp=2024-05-17T12:10:05.959Z
Expected Behaviour
if apply works next plan shouldn't fail with the error above
Actual Behaviour
apply works, plan thinks that resource does not exist
Steps to Reproduce
No response
Important Factoids
No response
References
The above happens when the key_vault_id references a key vault in another subscription
The text was updated successfully, but these errors were encountered:
Thanks for reporting this issue @4c74356b41. Unfortunately, in this case I would say that the bug actually lies with the successful apply. The provider is designed to operate per-subscription, and the azurerm_key_vault_key resource should not have applied that in the first place. You would need to use a provider alias scoped to the subscription containing the key vault in order to use this resource.
Is there an existing issue for this?
Community Note
Terraform Version
1.5.7
AzureRM Provider Version
3.75.0, 3.104.0
Affected Resource(s)/Data Source(s)
azurerm_key_vault_key
Terraform Configuration Files
Debug Output/Panic Output
Expected Behaviour
if apply works next plan shouldn't fail with the error above
Actual Behaviour
apply works, plan thinks that resource does not exist
Steps to Reproduce
No response
Important Factoids
No response
References
The above happens when the key_vault_id references a key vault in another subscription
The text was updated successfully, but these errors were encountered: