Add if (parAzBastionEnabled) to nsg create bastion #575
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.
Fixes #573
Overview/Summary
When setting Bastion to disabled the NSG is still deployed, expect that the NSG is not deployed
By adding if (parAzBastionEnabled) to the NSG creation this is fixed
This PR fixes/adds/changes/removes
Change hubNetworking.bicep line 368 with
Breaking Changes
None
Testing Evidence
NSG is not created ;-)
As part of this Pull Request I have
.bicep
file/s I am adding/editing are using the latest API version possiblemain
branch