handle ResourceGroup ScopeLocked error #831
Open
Conversation
This file contains 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
tony-schndr
requested review from
bennerv,
geoberle,
janboll,
weinong,
whober0521,
jharrington22,
SudoBrendan,
UlrichSchlueter and
zgalor
as code owners
geoberle
previously approved these changes
Nov 12, 2024
janboll
previously approved these changes
Nov 13, 2024
bennerv
reviewed
Nov 14, 2024
tooling/azure-automation/resources-cleanup/src/resources_cleanup.py
Outdated
Show resolved
Hide resolved
tony-schndr
force-pushed
the
fix-cleanup-resources
branch
from
3ce16ce
to
7154139
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
What this PR does
Fixes cleanup automation so the script does not fail when a resource group is ScopeLocked and missing persist=true.
Also ignores some python files and bumps requests as it was yanked.
Jira:
Link to demo recording:
Special notes for your reviewer