Terraform module to create vnet-peering resource on AZURE.
We eat, drink, sleep and most importantly love DevOps. We are working towards strategies for standardizing architecture while ensuring security for the infrastructure. We are strong believer of the philosophy Bigger problems are always solved by breaking them into smaller manageable problems. Resonating with microservices architecture, it is considered best-practice to run database, cluster, storage in smaller connected yet manageable pieces within the infrastructure.
This module is basically combination of Terraform open source and includes automatation tests and examples. It also helps to create and improve your infrastructure with minimalistic code instead of maintaining the whole infrastructure code yourself.
We have fifty plus terraform modules. A few of them are comepleted and are available for open source usage while a few others are in progress.
This module has a few dependencies:
IMPORTANT: Since the master
branch used in source
varies based on new modifications, we suggest that you use the release versions here.
Here are some examples of how you can use this module in your inventory structure:
module "vnet_peering" {
source = "clouddrove/vnet-peering/azure"
version = "1.0.0"
enabled_peering = true
resource_group_1_name = module.resource_group_1.resource_group_name
resource_group_2_name = module.resource_group_2.resource_group_name
different_rg = true
vnet_1_name = module.vnet.vnet_name[0]
vnet_1_id = module.vnet.vnet_id[0]
vnet_2_name = module.vnet_remote.vnet_name[0]
vnet_2_id = module.vnet_remote.vnet_id[0]
}
module "vnet_peering" {
source = "clouddrove/vnet-peering/azure"
version = "1.0.0"
enabled_diff_subs_peering = true
resource_group_1_name = module.resource_group_1.resource_group_name
diff_subs_resource_group_name = data.azurerm_resource_group.mgmt-rg.name
alias_subs_id = "82XXXXXXXXXXXXXXXXXXXXa80"
vnet_1_name = module.vnet.vnet_name[0]
vnet_1_id = module.vnet.vnet_id[0]
vnet_diff_subs_name = data.azurerm_virtual_network.mgmt-staging-vnet.name
vnet_diff_subs_id = data.azurerm_virtual_network.mgmt-staging-vnet.id
}
Name | Description | Type | Default | Required |
---|---|---|---|---|
alias_subs_id | Alias for remote provider in module. | string |
"" |
no |
allow_forwarded_traffic_vnet1 | Controls if forwarded traffic from VMs in the remote virtual network is allowed | bool |
false |
no |
allow_forwarded_traffic_vnet2 | Controls if forwarded traffic from VMs in the remote virtual network is allowed | bool |
false |
no |
allow_forwarded_traffic_vnet_diff_subs | Controls if forwarded traffic from VMs in the remote virtual network is allowed | bool |
false |
no |
allow_gateway_transit_vnet1 | Controls gatewayLinks can be used in the remote virtual network’s link to the local virtual network. | bool |
false |
no |
allow_gateway_transit_vnet2 | Controls gatewayLinks can be used in the remote virtual network’s link to the local virtual network. | bool |
false |
no |
allow_gateway_transit_vnet_diff_subs | Controls gatewayLinks can be used in the different subscription virtual network’s link to the local virtual network. | bool |
false |
no |
allow_virtual_network_access | Controls if the VMs in the remote virtual network can access VMs in the local virtual network. | bool |
true |
no |
attributes | Additional attributes (e.g. 1 ). |
list(string) |
[] |
no |
diff_subs_resource_group_name | The name of remote resource group to be imported. | string |
"" |
no |
different_rg | Flag to tell whether peering is to be done in same in resource group or different resource group | bool |
false |
no |
enabled_diff_subs_peering | n/a | bool |
false |
no |
enabled_peering | Set to false to prevent the module from creating any resources. | bool |
false |
no |
environment | Environment (e.g. prod , dev , staging ). |
string |
"" |
no |
label_order | Label order, e.g. sequence of application name and environment name ,environment ,'attribute' [webserver ,qa ,devops ,public ,] . |
list(any) |
[] |
no |
name | Name (e.g. app or cluster ). |
string |
"" |
no |
repository | Terraform current module repo | string |
"" |
no |
resource_group_1_name | The name of 1st existing resource group to be imported. | string |
"" |
no |
resource_group_2_name | The name of 2nd existing resource group to be imported. | string |
"" |
no |
use_remote_gateways_vnet1 | Controls if remote gateways can be used on the local virtual network | bool |
false |
no |
use_remote_gateways_vnet2 | Controls if remote gateways can be used on the local virtual network | bool |
false |
no |
use_remote_gateways_vnet_diff_subs | Controls if remote gateways can be used on the different subscription virtual network | bool |
false |
no |
vnet_1_id | The full Azure resource ID of the remote virtual network. Changing this forces a new resource to be created. | string |
"" |
no |
vnet_1_name | The name of the virtual network. Changing this forces a new resource to be created. | string |
"" |
no |
vnet_2_id | The full Azure resource ID of the remote virtual network. Changing this forces a new resource to be created. | string |
"" |
no |
vnet_2_name | The name of the remote virtual network. | string |
"" |
no |
vnet_diff_subs_id | The id of the remote virtual network. | string |
"" |
no |
vnet_diff_subs_name | The name of the remote virtual network. | string |
"" |
no |
Name | Description |
---|---|
vnet_peer_1_id | The id of the newly created virtual network peering in on first virtual netowork. |
vnet_peer_1_name | The name of the newly created virtual network peering in on first virtual netowork. |
vnet_peer_2_id | The id of the newly created virtual network peering in on second virtual netowork. |
vnet_peer_2_name | The name of the newly created virtual network peering in on second virtual netowork. |
vnet_peer_diff_subs_id | The id of the newly created virtual network peering in on different subscription virtual netowork. |
vnet_peer_diff_subs_name | The name of the newly created virtual network peering in on different subscription virtual netowork. |
In this module testing is performed with terratest and it creates a small piece of infrastructure, matches the output like ARN, ID and Tags name etc and destroy infrastructure in your AWS account. This testing is written in GO, so you need a GO environment in your system.
You need to run the following command in the testing folder:
go test -run Test
If you come accross a bug or have any feedback, please log it in our issue tracker, or feel free to drop us an email at [email protected].
If you have found it worth your time, go ahead and give us a ★ on our GitHub!
At CloudDrove, we offer expert guidance, implementation support and services to help organisations accelerate their journey to the cloud. Our services include docker and container orchestration, cloud migration and adoption, infrastructure automation, application modernisation and remediation, and performance engineering.
We are The Cloud Experts!
We ❤️ Open Source and you can check out our other modules to get help with your new Cloud ideas.