Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat: Updated Network Manager module to support Routing Configuration…
… feature (#4096) ## Description Azure Virtual Network Manager (AVNM) recently introduced a new feature that allows users to configure routing settings for their virtual networks. See [concept-user-defined-route](https://learn.microsoft.com/en-us/azure/virtual-network-manager/concept-user-defined-route) documentation. ℹ️ Routing Configuration is Generally Available in many Azure regions: See [UDR Management - General Availability](https://learn.microsoft.com/en-us/azure/virtual-network-manager/concept-user-defined-route#general-availability). Given the optional usage of this feature, This should not impact existing usage of AVNM. While enabling this feature, the following had to be updated on the module: - Added new child modules for `routing-configuration`, `rule-collection` and `rule`. - Updated the API to `2024-05-01` as per (https://learn.microsoft.com/en-us/azure/templates/microsoft.network/networkmanagers?pivots=deployment-language-bicep) - Updated module version. - Use of the common types for `roleAssignments` and `locks`. - Update the scope access to become optional as AVNM now enables a `None` feature mode to support capabilities like IPAM and Virtual Network Verifier. - Updated built in role name from `IPAM Pool Contributor` to `IPAM Pool User`, Still keeps the same GUID. - Added support for `memberType` for Subnets for Network Groups to support the new routing feature. However, set the default to virtual network as it is the common scenario. - Updated the default test case to not use any features. - Expanded on the max test case coverage to include the routing feature and added different network groups of subnet types. - Expanded on usage of the `import` functionality to reduce code duplication and import types from child module to parents. <!-- >Thank you for your contribution ! > Please include a summary of the change and which issue is fixed. > Please also include the context. > List any dependencies that are required for this change. Fixes #123 Fixes #456 Closes #123 Closes #456 --> ## Pipeline Reference <!-- Insert your Pipeline Status Badge below --> | Pipeline | | -------- | | [](https://github.com/ahmadabdalla/bicep-registry-modules/actions/workflows/avm.res.network.network-manager.yml) | ## Type of Change <!-- Use the checkboxes [x] on the options that are relevant. --> - [ ] Update to CI Environment or utilities (Non-module affecting changes) - [ ] Azure Verified Module updates: - [ ] Bugfix containing backwards-compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in `version.json`: - [ ] Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description. - [ ] The bug was found by the module author, and no one has opened an issue to report it yet. - [x] Feature update backwards compatible feature updates, and I have bumped the MINOR version in `version.json`. - [ ] Breaking changes and I have bumped the MAJOR version in `version.json`. - [ ] Update to documentation ## Checklist - [x] I'm sure there are no other open Pull Requests for the same update/change - [x] I have run `Set-AVMModule` locally to generate the supporting module files. - [x] My corresponding pipelines / checks run clean and green without any errors or warnings <!-- Please keep up to date with the contribution guide at https://aka.ms/avm/contribute/bicep -->
- Loading branch information