This repository has been archived by the owner on Nov 27, 2020. It is now read-only.
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
There is usually situation when you need to override the default route of VNET or vnet peering by your custom rule which defines custom next hop (e.g. azure firewall). VNET can define multiple address spaces not only one. It is handy to define them as array. Of course it could be defined separately as new entry with new name and its address space - if you don't find it use-full, feel free to abandon the PR. The name of such route entry is then created by concatenation of the "route entry name" + "address space".
Enhancement
Example of tfvars
Tested: