Closed Xander-Rudolph closed 4 years ago
Thanks for reporting this! I think that this is an issue to be addressed in the AzureRM Terraform provider, rather than in core. I'm going to label it as such, and the HashiBot will shortly migrate it over to the provider GitHub repository. Please feel free to re-open this if they determine that it is indeed an issue that needs to be addressed in Terraform core.
This issue has been automatically migrated to terraform-providers/terraform-provider-azurerm#8199 because it looks like an issue with that provider. If you believe this is not an issue with the provider, please reply to terraform-providers/terraform-provider-azurerm#8199.
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.
When trying to use azurerm_mssql_server_vulnerability_assessment and referencing a storage container path that is in a different subscription, it fails to find the storage account. I had tried to use a different provider and a data command to try to force the connection to the right place, but data and the azurerm_mssql_server_vulnerability_assessment's don't appear to support a different provider.
Terraform Version
Terraform v0.12.28
Expected Behavior
Because storage names are unique, I would expect the assessment is able to find the resource the same way that the azurerm_mssql_server_security_alert_policy or azurerm_sql_server (in extended_auditing_policy) does while the resource is in a different subscription.
Actual Behavior
It fails to find the storage account and throws the following error:
Steps to Reproduce
References
https://www.terraform.io/docs/providers/azurerm/r/mssql_server_vulnerability_assessment.html
Sample Code