-
Notifications
You must be signed in to change notification settings - Fork 571
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
Network gateway default parameters #925
Network gateway default parameters #925
Conversation
@microsoft-github-policy-service agree |
/azp run unit |
Azure Pipelines successfully started running 1 pipeline(s). |
Hi @chrsundermann please can you run |
Hi @matt-FFFFFF, I executed |
/azp run unit |
Azure Pipelines successfully started running 1 pipeline(s). |
Hi @matt-FFFFFF, |
Minimum provider versions. Also there's a mapping missing as the data traverses through the module somewhere too |
/azp run unit |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run unit |
Azure Pipelines could not run because the pipeline triggers exclude this branch/path. |
Thanks for this - I've pulled into the ama branch for the next major release |
@chrsundermann I had to add null values to the corresponding VPN gateway object in order for the values to be preserved when they are azurerm_virtual_network_gateway_vpn = [
for location, hub_network in local.hub_networks_by_location :
{
# ...
remote_vnet_traffic_enabled = null
virtual_wan_traffic_enabled = null |
Thanks for the update @matt-FFFFFF. Could only check with ExpressRoute setup. This was successfully deployed at customer site. |
I don't think the attributes are valid for VPN but since all list members have to have same schema, needed to add as nulls. |
Overview/Summary
This is the Pull Request for the issue #924.
This PR fixes/adds/changes/removes
Breaking Changes
Testing Evidence
Terraform plan before changes:
Terraform plan after changes shows "Nothing to change".
As part of this Pull Request I have
main
branch