Changed ArmApiControl path to get VNetGW on the selected VNet Subscrition #342
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
vivalada
requested review from
michielvanschaik,
jchancellor-ms and
shaunjacob
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Overview/Summary
Fixing a Portal UI bug that, in the Azure Connectivity tab, was not allowing the selection of a VNet Gateway on a different Subscription that the one where the AVS is being deployed.
This PR fixes/adds/changes/removes
Breaking Changes
Testing Evidence
Provided in the related ADO Item.
As part of this Pull Request I have
mainbranch