New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix provision state after down #2837
Conversation
I mentioned this internally to Victor, but I think we want the semantics of |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we want to defer the work to findCompletedDeployments to get this fix in the tree, I'm fine with that. Let's just follow up with an issue if either azd env refresh
or azd down
behave oddly with just this fix (my expectation is that both of these commands should error in some way after you have run azd down
to remove all the infrastructure, but I'm not sure if they will.)
Issue created: #2842 Running I think we can have the fix for the other issue for 1.5.0, as it is usually not expected to run azd down multiple times, and it is not a blocker to the regular create+delete flows. |
Azure Dev CLI Install InstructionsInstall scriptsMacOS/Linux
bash:
pwsh:
WindowsPowerShell install
MSI install
Standalone Binary
MSIContainer
Documentationlearn.microsoft.com documentationtitle: Azure Developer CLI reference
|
fix: #2835