-
Notifications
You must be signed in to change notification settings - Fork 90
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
Add feature flags for Hub/Spoke resources #153
Labels
Comments
|
Could we add the flag whether or not hub is required in the deployment? Customer may only need the spoke vnet and did not want to connect to any hub. Or at least, create a hub placeholder with/without firewall or bastion |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Customers have use-cases that may involve bringing their own resources (for example, an existing hub configuration)
Would like to refactor the bicep/terraform templates to accommodate for optional infrastructure resources being created and give the user set number of options on types of existing resources they can bring in.
The text was updated successfully, but these errors were encountered: