Implemented dual Terraform scenarios for both traditional hub-and-spoke and virtual wan #156
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Pull Request for Implementing Virtual WAN and Traditional Hub and Spoke Architectures
Overview/Summary
This Pull Request introduces infrastructure as code changes that successfully implement two distinct Azure network architectures: a traditional Hub and Spoke model and a comprehensive Virtual WAN setup. Key highlights include the integration of Azure Bastion for secure connectivity, the establishment of Firewall Policies for network security, and essential connectivity resources across both scenarios.
This PR fixes/adds/changes/removes
hubnetworking
andvirtual_network_gateway
modules.Breaking Changes
None introduced.
Testing Evidence
The Terraform configuration files have been tested, yielding the following planned actions during deployment:
All planned changes have been executed using
terraform apply
, following the shown plan without errors. The successful deployment was verified through connectivity tests within both scenarios, confirming the intended network operations.As part of this Pull Request I have
main
branchTerraform execution plan and subsequent application of the code led to the successful creation, update, and integration of networking resources as designed. Witnessed is the orchestration of creating and updating Azure resources with Terraform's operations. The warnings observed regarding the argument deprecation have been noted, and an update to the code to use the newer property before provider upgrade to version 4.0 is in the plan. The introduction of Azure Virtual WAN between branches offers significant advancements in routing simplicity and operational efficiency. The integration of Azure Bastion across both deployments centralizes and secures administrative access, marking a pivotal step in network management.