Troubleshoot Azure DevOps guide: Issues arise when there's an existing resource group in the same subscription
chengyineng38 opened this issue · comments
Problem: I configured my resource group to be mlops-stack-ado
but there already exists another resource group in the same subscription.
Fix: I manually changed all resource group names and storage account names to avoid the clash, but Terraform is not happy. I eventually fixed the clashes by running terraform init -reconfigure
and terraform init -migrate-state
in:
databricks-config/staging
databricks-config/prod
.mlops-setup-scripts/cicd
In hindsight, it probably would have been easier to just start the project from scratch, supplying different resource group and storage account names. Hope this helps someone out there!
Closing this issue since as of https://github.com/databricks/mlops-stack/releases/tag/v0.1 we replaced Terraform.