docs: enhance AVM Post Deployment Guide with additional parameter passing options for scripts#802
Merged
Avijit-Microsoft merged 2 commits intodevfrom Mar 9, 2026
Merged
Conversation
…sing options for scripts
Pavan-Microsoft
requested review from
Avijit-Microsoft,
Prajwal-Microsoft,
Roopan-Microsoft,
Vinay-Microsoft,
aniaroramsft,
brittneek,
dgp10801,
nchandhi and
toherman-msft
as code owners
Pavan-Microsoft
temporarily deployed
to
production
GitHub Actions
Inactive
Pavan-Microsoft
temporarily deployed
to
production
GitHub Actions
Inactive
Avijit-Microsoft
approved these changes
Mar 9, 2026
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.
Purpose
This pull request updates the
AVMPostDeploymentGuide.mddocumentation to provide clearer instructions for running deployment scripts, including options for passing all parameters manually. The changes make it easier for users to execute scripts in environments whereazd envis not configured.Expanded script usage instructions:
run_create_agents_scripts.sh, allowing users to specify all required arguments directly.process_sample_data.sh, detailing all required arguments for environments withoutazd env.process_custom_data.shby requiring<Resource-Group-Name>and providing manual parameter instructions for users withoutazd env.Does this introduce a breaking change?