fix: AVM guidelines & version issue fix #477
Merged
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 deployment flexibility, documentation, and resource tagging for the Document Knowledge Mining Solution Accelerator. The main changes include enhanced support for both AVM and azd deployment methods in scripts and documentation, improved resource tagging for traceability, an upgrade to the AKS Kubernetes version, and more robust handling of deployment outputs in PowerShell scripts.
Deployment & Script Improvements
ResourceGroupNameparameter toresourcedeployment.ps1, enabling post-deployment configuration for AVM, ARM/Bicep, and custom template deployments. The script now detects the deployment method and maps outputs accordingly. [1] [2] [3] [4] [5]DeploymentGuide.mdand added a newAVMPostDeploymentGuide.mdto clarify deployment steps for both azd and AVM users, including explicit instructions for script usage and post-deployment configuration. [1] [2]Resource Tagging & Metadata
DeploymentNameandCreatedByfield for better traceability of deployments and ownership in both Bicep and JSON templates. [1] [2] [3]Infrastructure Updates
1.30.4to1.32.7in both Bicep and JSON templates to ensure compatibility and access to new features. [1] [2]Other Enhancements
These changes collectively improve the deployment experience, make post-deployment steps clearer for different user scenarios, and enhance resource management and traceability.
Does this introduce a breaking change?
Golden Path Validation
Deployment Validation
What to Check
Verify that the following are valid
Other Information