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

Ability to use existing ddos for hub vnet Feature Request #1222

Open
Karmeshs opened this issue Jan 13, 2025 · 0 comments
Open

Ability to use existing ddos for hub vnet Feature Request #1222

Karmeshs opened this issue Jan 13, 2025 · 0 comments

Comments

@Karmeshs
Copy link

Community Note

  • 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

Is your feature request related to a problem?

I would reaaly like to have the option to use an existing ddos service for the hub Vnet instead of the present options which either disables it or creates a new one if enabled. DDoS is an expensive service & we have already created one post deployment of the LZ (using another terraform script) which we are using across all our spokes too.

When I run the terraform script for the LZ now, it is creating a new ddos & replacing it with our existing one on the hub vnet. If I disable the ddos in network settings option then it disassociates the existing ddos from the hub.

Describe the solution you'd like

I would like to have the option to add/use an existing ddos for the hub using the existing ddos id.

Additional context

@Karmeshs Karmeshs changed the title Feature Request Ability to use existing ddos for hub vnet Feature Request Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant