You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Versions
terraform: 1.9.4
azure provider: 3.115.0
module: Connectivity
Description
Describe the bug
Deploying vWAN with private DNS zones, only links to the unsecured virtual networks, not the secured virtual networks
Steps to Reproduce
Create a deployment with vWAN configuration, non-secure and secure spokes, enable Private DNS links
Deploy config, and will see that only the non-secure virtual networks get links created
Screenshots
Additional context
To resolve, update line 1684 of modules/connectivity/locals.tf as per below
from
for spoke_resource_id in virtual_hub_config.config.spoke_virtual_network_resource_ids :
to
for spoke_resource_id in concat(virtual_hub_config.config.spoke_virtual_network_resource_ids, virtual_hub_config.config.secure_spoke_virtual_network_resource_ids) :
The text was updated successfully, but these errors were encountered:
…network ids (#1107)
#1106
Updated spoke_virtual_networks_for_dns to include the secure virtual
network ids
<!-- markdownlint-disable first-line-h1 -->
<!-- Thank you for submitting a Pull Request. Please fill out the
template below.-->
## Overview/Summary
Replace this with a brief description of what this Pull Request fixes,
changes, etc.
## This PR fixes/adds/changes/removes
1. *Replace me*
2. *Replace me*
3. *Replace me*
### Breaking Changes
1. *Replace me*
2. *Replace me*
## Testing Evidence
Please provide any testing evidence to show that your Pull Request
works/fixes as described and planned (include screenshots, if
appropriate).
## As part of this Pull Request I have
- [ ] Checked for duplicate [Pull
Requests](https://github.com/Azure/terraform-azurerm-caf-enterprise-scale/pulls)
- [ ] Associated it with relevant
[issues](https://github.com/Azure/terraform-azurerm-caf-enterprise-scale/issues),
for tracking and closure.
- [ ] Ensured my code/branch is up-to-date with the latest changes in
the `main`
[branch](https://github.com/Azure/terraform-azurerm-caf-enterprise-scale/tree/main)
- [ ] Performed testing and provided evidence.
- [ ] Updated relevant and associated documentation.
Community Note
Versions
terraform: 1.9.4
azure provider: 3.115.0
module: Connectivity
Description
Describe the bug
Deploying vWAN with private DNS zones, only links to the unsecured virtual networks, not the secured virtual networks
Steps to Reproduce
Screenshots
Additional context
To resolve, update line 1684 of modules/connectivity/locals.tf as per below
from
for spoke_resource_id in virtual_hub_config.config.spoke_virtual_network_resource_ids :
to
for spoke_resource_id in concat(virtual_hub_config.config.spoke_virtual_network_resource_ids, virtual_hub_config.config.secure_spoke_virtual_network_resource_ids) :
The text was updated successfully, but these errors were encountered: