Skip to content
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

[Bug] Running azd up after running azd down doesn't make changes to Azure #2835

Closed
john0isaac opened this issue Oct 5, 2023 · 5 comments · Fixed by #2837
Closed

[Bug] Running azd up after running azd down doesn't make changes to Azure #2835

john0isaac opened this issue Oct 5, 2023 · 5 comments · Fixed by #2837
Assignees
Labels
bug Something isn't working command core customer-reported identify a customer issue needs-team-attention Issues out of a milestone question

Comments

@john0isaac
Copy link
Contributor

Output from azd version
azd version 1.4.0 (commit 25dc100)

Describe the bug
After running the down command that deletes the resources from Azure if you try to recreate the deleted resources using the up command it gives you a message that says "(-) Skipped: Didn't find new changes." and doesn't create anything on Azure.

To Reproduce
Run azd up
Run azd down
Run azd up

Expected behavior
The deleted resources get created again on Azure.

Additional context
image

@john0isaac
Copy link
Contributor Author

@savannahostrowski that is the issue that I told you about I tried multiple times and it's consistent.

@john0isaac john0isaac changed the title [Bug] Running azd up after running azd down doesn't make changes to Azure [Bug] Running azd up after running azd down doesn't make changes to Azure Oct 5, 2023
@savannahostrowski
Copy link
Contributor

Hey @john0isaac! Thanks for following up.

@rajeshkamal5050 Can we investigate this?

@rajeshkamal5050
Copy link

@vhvb1989 looks like even though the resources are deleted(azd down). The subsequent provisioning(azd up) checks against the previous deployment runs and skips/does nothing. Seems to be a bug. Can you take a look?

@rajeshkamal5050 rajeshkamal5050 added the bug Something isn't working label Oct 5, 2023
@rajeshkamal5050 rajeshkamal5050 added this to the November 2023 - 1.5.0 milestone Oct 5, 2023
@microsoft-github-policy-service microsoft-github-policy-service bot added the needs-team-attention Issues out of a milestone label Oct 5, 2023
@vhvb1989
Copy link
Member

vhvb1989 commented Oct 5, 2023

@john0isaac , thank you for reporting this.

I'm working/debugging the issue. As a workaround, for now, you can call azd provision --no-state to re-deploy your infrastructure

@vhvb1989
Copy link
Member

vhvb1989 commented Oct 6, 2023

fix expected as part of 1.4.1 within a few more minutes now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working command core customer-reported identify a customer issue needs-team-attention Issues out of a milestone question
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants