refactor: added post-deployment guide and updated post deployment scripts for users deployed using AVM template #550
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 introduces significant improvements to the post-deployment experience for the Multi-Agent Custom Automation Engine Solution Accelerator, especially for users deploying via Azure Verified Modules (AVM). The changes include a new, detailed post-deployment guide, enhanced automation scripts for configuration and data setup, improved resource and subscription detection, and tagging enhancements for better traceability.
Documentation enhancements:
AVMPostDeploymentGuide.md
to help users complete post-deployment steps after AVM deployments, including prerequisites, step-by-step instructions, and troubleshooting tips.Automation and configuration improvements:
Team-Config-And-Data.ps1
to automatically detect deployment method, retrieve configuration values from eitherazd
environment or Azure deployment outputs, and guide users through Azure subscription selection and authentication, reducing manual input and errors.Process-Sample-Data.ps1
,Upload-Team-Config.ps1
, andprocess_sample_data.sh
scripts to accept and propagateAzSubscriptionId
, ensuring correct resource targeting and subscription context during automation. [1] [2] [3] [4] [5] [6]Infrastructure and resource tagging:
main.bicep
andmain_custom.bicep
by adding aDeploymentName
tag, improving traceability of deployments and simplifying output retrieval for post-deployment automation. [1] [2]Minor code fixes:
index_datasets.py
to ensure both.csv
and.json
file extensions are handled correctly when generating dataset titles.Does this introduce a breaking change?
How to Test
What to Check
Verify that the following are valid
Other Information