Fix Tier3 Naming Convention - Add more flexibility and match mlz.bice… #730
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
…p (core) Azure#729 This Fix fixes the naming convention (Prefix instead of workload) and allows the workload name to be sent as a parameter. Since the workload name could be anything sent by the user, and the storage account name should have additional considerations (like the option to also be a parameter)
Adding parameters for workloadName and workloadLogStorageAccountNameParameter to the tier 3 readme
Fixing Lint Error in Tier3 Readme
lisamurphy-msft
approved these changes
Sep 7, 2022
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.
…p (core) #729
This Fix fixes the naming convention (Prefix instead of workload) and allows the workload name to be sent as a parameter. Since the workload name could be anything sent by the user, and the storage account name should have additional considerations (like the option to also be a parameter)
Issue reference
The issue this PR will close: #729
Checklist
Please make sure you've completed the relevant tasks for this PR out of the following list: