-
Notifications
You must be signed in to change notification settings - Fork 587
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
Question: hub_routing_preference #861
Comments
Hi @hannesbreit We don't expose these settings at the moment. We will add these to the backlog for prioritisation. |
Thanks @matt-FFFFFF |
You could use It can update a resource properties. |
any plan on that. Also facing the same issue and the az api update resource helps but have the different state with the modules so that it always destroy and recreate. Will be great to have the properties directly from caf |
Can you ignore the property in the azurerm resource and only manage through azapi? |
Thanks for the answer. As i know it s not possible to ignore changes on Modules. Is this possible by Caf some how? |
No of course not, my apologies. |
@matt-FFFFFF sorry to ping you. There is a PR #930 by a colleague. Can we do something to get this merged? We are making changes outside of terraform at the moment, because we can't run tf without resetting the routing preference. It would be appreciated, that someone could have a look at that PR to fix that. |
Community Note
Versions
terraform: 1.6.2
azure provider: azurerm.connectivity
module: connectivity
Description
Describe the bug
Steps to Reproduce
For virtual WAN deployment, I try to set the hub_routing_preference to "ASpath" for a specific Hub but I don't see this documented anywhere. Also other settings like "virtual_router_auto_scale_min_capacity" are missing.
I tried to put these settings somehow into the "advanced" section and also in the "custom_settings_by_resource_type" but without success.
Can someone help, guide or post a link where I can find this in the documentation (I was not able to find it there).
The text was updated successfully, but these errors were encountered: