Azure: Delete resource groups between all samples runs.#47
Merged
Conversation
DrisDary
requested review from
alexlave100,
bblommers,
bryansan-local and
paolosalvatori
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Previously, resource group cleanup between sample runs only happened for Bicep samples. Script-based samples like web-app-cosmosdb-mongodb-api and web-app-sql-database had no cleanup between them — only a docker system prune which cleans Docker but not the emulator's state. This meant resources from one sample (like a webapp named local-webapp-test) would still exist when the next sample ran, causing state pollution. We moved the resource group deletion block out of the Bicep-only conditional so it now runs after every sample, giving each one a clean slate.