This repository has been archived by the owner on Feb 14, 2024. It is now read-only.
feat(module/vnet): add possibility to re-use existing subnets #219
Conversation
This file contains 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
FoSix
commented
Dec 6, 2022
migara
approved these changes
Dec 8, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Description
Extend brownfield deployments by re-using not only existing VNET but also existing Subnets.
Motivation and Context
Based on real life examples where deployment is done in an already existing VNET + Subnets. This module allowed only to re-use an existing VNET and forced creation of Subnets. With this change only NSGs and UDRs are being created and assigned to already existing Subnets. Subnet definition structure does not change.
How Has This Been Tested?
A modified VNET example was used to test the code.
Screenshots (if appropriate)
Types of changes
Checklist