feat: Network module changes and fix #287
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 several improvements and standardizations to the infrastructure codebase, focusing on parameter naming consistency, enhanced deployment configuration, and resource naming conventions. The changes affect both parameter files and Bicep modules, aiming to improve maintainability and clarity across the deployment templates.
Parameter and Naming Standardization:
environmentNameparameter tosolutionNamein bothinfra/main.parameters.jsonandinfra/main.waf.parameters.jsonfor consistency across deployment parameter files. [1] [2]main.parameters.waf.jsontomain.waf.parameters.jsonfor improved clarity and organization.Deployment Configuration Enhancements:
infra/main.waf.parameters.jsonto support monitoring, scalability, and VM administration, includingexistingFoundryProjectResourceId,enableMonitoring,enableScalability,virtualMachineAdminUsername, andvirtualMachineAdminPassword. Also standardized boolean values to unquotedtrue.Resource Naming and Convention Updates:
container-registry.bicep,key-vault.bicep,log-analytics-workspace.bicep) to use thetakefunction for generating deterministic, length-constrained names, improving ARM template deployment reliability. [1] [2] [3]virtualNetwork.bicepto lowercase (containers,nsg-containers) to maintain naming consistency and avoid potential case-sensitivity issues.Does this introduce a breaking change?
Golden Path Validation
Deployment Validation
What to Check
Verify that the following are valid
Other Information