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
Initial Azure deployments are successful but the subsequent deployments fail because the Nebari schema generates a new postfix if the storage_account_postfix field is not set in the nebari-config.yaml; this was how it was prior to the extension-mechanism.
The second deployment fails because a new random postfix is generated and this causes the Terraform state to delete the storage account and the state and then the deployment grinds to a halt.
Expected behavior
To successfully redeploy Azure.
OS and architecture in which you are running Nebari
MacOS
How to Reproduce the problem?
Deploy Azure twice from the @develop branch.
Command output
No response
Versions and dependencies used.
No response
Compute environment
Azure
Integrations
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Describe the bug
Initial Azure deployments are successful but the subsequent deployments fail because the Nebari schema generates a new postfix if the storage_account_postfix field is not set in the nebari-config.yaml; this was how it was prior to the extension-mechanism.
The second deployment fails because a new random postfix is generated and this causes the Terraform state to delete the storage account and the state and then the deployment grinds to a halt.
Expected behavior
To successfully redeploy Azure.
OS and architecture in which you are running Nebari
MacOS
How to Reproduce the problem?
Deploy Azure twice from the
@develop
branch.Command output
No response
Versions and dependencies used.
No response
Compute environment
Azure
Integrations
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: