Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/mosowaz/azure_ci_cd_pipeline_for_terraform_code
Using Azure ci cd Pipeline for Terraform code to create or destroy resources in Azure Portal
https://github.com/mosowaz/azure_ci_cd_pipeline_for_terraform_code
azure-devops terraform-azure-pipeline
Last synced: 2 days ago
JSON representation
Using Azure ci cd Pipeline for Terraform code to create or destroy resources in Azure Portal
- Host: GitHub
- URL: https://github.com/mosowaz/azure_ci_cd_pipeline_for_terraform_code
- Owner: mosowaz
- License: mit
- Created: 2024-11-28T10:40:53.000Z (2 months ago)
- Default Branch: main
- Last Pushed: 2025-01-20T16:12:42.000Z (21 days ago)
- Last Synced: 2025-01-20T17:26:33.220Z (21 days ago)
- Topics: azure-devops, terraform-azure-pipeline
- Language: HCL
- Homepage:
- Size: 94.7 KB
- Stars: 1
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
[](https://dev.azure.com/MosesOwaseye/hub%20and%20spokes%20vnet%20peering/_build/latest?definitionId=10&branchName=main)
# Azure_CI_CD_Pipeline_for_Terraform_with_SPN
Using Azure ci cd Pipeline for Terraform code to create, modify or destroy resources in Azure Portal
### Connect Hub and Spoke virtual networks with virtual network peering using Terraform code
## Order of code
./network/main.tf --> ./compute/main.tf --> ./rt_table-nsg/main.tf
## Description
### Note
The providers version are pinned to a specific version.\
terraform version = 1.9.5\
azurerm version = 4.0.1
### ./network
1. Create 2 Spoke virtual networks and 1 Hub vnet
2. Peer Hub virtual network with both Spoke virtual networks
- azurerm_virtual_network_peering.peering1-2 (hub vnet to spoke1 vnet)
- azurerm_virtual_network_peering.peering2-1 (spoke1 vnet to hub vnet)
- azurerm_virtual_network_peering.peering1-3 (hub vnet to spoke2 vnet)
- azurerm_virtual_network_peering.peering3-1 (spoke2 vnet to hub vnet)
3. Create subnets in each virtual network - (vnet1-subnet, vnet2-subnet, and vnet3-subnet)
### ./compute
1. Create data source block to reference network resources (in data.tf)
2. Deploy a virtual machine (VM) into each virtual network (hub-vm, spoke1-vm, and spoke2-vm)
- Create public ip for "hub-vm" (which is a Virtual Appliance)
- Configure the "hub-vm" to allow ip forwarding in the user_data section
- Introduce Provisioner "local-exec" to save the public IP address on local machine as a text file
### ./rt_table-nsg
1. Create network security group, security rules, and rule associtaion
- "inbound-public" to allow local machine to connect to public ip of hub and spoke VMs
- "outbound-private" to allow access from other subnets within Azure
2. Create route tables and associations
- route table "spoke1-2", next hop is NVA, and destination is "vnet3-subnet".\
Then, associate the table with "vnet2-subnet"
- route table spoke2-1", next hop is NVA, and destination is "vnet2-subnet".\
Then, associate the table with "vnet3-subnet"
3. Test route between both spokes VM
- ssh into NVA (hub-vm), and reboot it for IP forwarding configuration to take effect
- Connect to each Spoke VM, ping and tracepath command to each other to confirm next hop.
- Next hop should show "hub-vm"
## Test result showing tracepath and next hop between each Spoke VMs
