[release/8.0] Generate and store random RG name when provisioning #3508
Conversation
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
…ioner.cs Co-authored-by: Eric Erhardt <[email protected]>
ghost
added
the
area-app-model
dotnet-policy-service
bot
added
the
Servicing-consider
danmoseley
reviewed
Apr 9, 2024
sebastienros
approved these changes
Apr 9, 2024
danmoseley
approved these changes
Apr 10, 2024
Closed
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Backport of #3375 to release/8.0
/cc @davidfowl @sebastienros
Customer Impact
Deployments are using the machine name in the resource group name. This change uses a random number and stores the created resource group name in user secrets.
Testing
Manual validation of:
Risk
Low. Users can also still force a custom resource group name.
Regression?
No.
Microsoft Reviewers: Open in CodeFlow