Add flow_timeout_in_minutes to VNETs. #663
Merged
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.
Problem
When either using a Firewall in a brown field deployment or deploying a firewall through SDAF in a green field deployment. It's important to set the VNET flow timeout in accordance with the Firewall idle timeout.
As the idle timeout can be increased only by request to Microsoft support, we can't infer the actual value to set and should therefore delegate to the users.
Furthermore, when having a firewall not controlled by SDAF, it should be possible to disable route propagation on route tables manually.
Solution
Add the option to specify
*_flow_timeout_in_minutes
for management and workload zone VNETs, defaults tonull
.Add the option to specify
network_enable_route_propagation
for subnet route tables, defaults totrue
.