This repository was archived by the owner on Jan 11, 2023. It is now read-only.
Doc update: attach route table to VNET #1627
Merged
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
JackQuincy
reviewed
Oct 19, 2017
docs/custom-vnet.md
Outdated
|
|
||
| ``` | ||
| #!/bin/bash | ||
| rt=$(az network route-table list -g acs-custom-vnet | jq -r '.[].name') |
There was a problem hiding this comment.
.name only works if they are in the same resource group. . .[].id should work even if the vnet is in a different resource group.
ghost
removed
the
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.
What this PR does / why we need it: In our custom VNET docs it doesn't mention the need to attach the created cluster's route table to the custom VNET
Release note: