Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Make allowForwardedTraffic and allowGatewayTransit configurable for hub peering #347

Open
djbark opened this issue Mar 7, 2024 · 0 comments
Labels
enhancement New feature or request
Milestone

Comments

@djbark
Copy link

djbark commented Mar 7, 2024

  • 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.

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.

@matt-FFFFFF matt-FFFFFF added the enhancement New feature or request label Mar 7, 2024
@matt-FFFFFF matt-FFFFFF added this to the v5.0 milestone Jun 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants