You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment
Description
allowForwardedTraffic and allowGatewayTransit are defaulted to true for peering_hub_outbound. As a I have firewall within the hub network that all traffic needs to be forced through (even between spokes) I would like the ability to set these to false.
I see this is mentioned in #264 but raising a new request for visibility as this is an issue for me and I would rather not write my own custom peering.
The text was updated successfully, but these errors were encountered:
Description
allowForwardedTraffic and allowGatewayTransit are defaulted to true for peering_hub_outbound. As a I have firewall within the hub network that all traffic needs to be forced through (even between spokes) I would like the ability to set these to false.
Describe the solution you'd like
These additional input variables to be added:
hub_peering_allow_forwarded_traffic
hub_peering_allow_gateway_transit
Additional context
I see this is mentioned in #264 but raising a new request for visibility as this is an issue for me and I would rather not write my own custom peering.
The text was updated successfully, but these errors were encountered: