github.com/brandonstevens/terraform@v0.9.6-0.20170512224929-5367f2607e16/examples/azure-vnet-to-vnet-peering/README.md (about) 1 # VNET to VNET Peering 2 3 This template creates two VNETs in the same location, each containing a single subnet, and creates connections between them using VNET Peering. 4 5 ## main.tf 6 The `main.tf` file contains the actual resources that will be deployed. It also contains the Azure Resource Group definition and any defined variables. 7 8 ## outputs.tf 9 This data is outputted when `terraform apply` is called, and can be queried using the `terraform output` command. 10 11 ## provider.tf 12 You may leave the provider block in the `main.tf`, as it is in this template, or you can create a file called `provider.tf` and add it to your `.gitignore` file. 13 14 Azure requires that an application is added to Azure Active Directory to generate the `client_id`, `client_secret`, and `tenant_id` needed by Terraform (`subscription_id` can be recovered from your Azure account details). Please go [here](https://www.terraform.io/docs/providers/azurerm/) for full instructions on how to create this to populate your `provider.tf` file. 15 16 ## terraform.tfvars 17 If a `terraform.tfvars` file is present in the current directory, Terraform automatically loads it to populate variables. We don't recommend saving usernames and password to version control, but you can create a local secret variables file and use `-var-file` to load it. 18 19 If you are committing this template to source control, please insure that you add this file to your `.gitignore` file. 20 21 ## variables.tf 22 The `variables.tf` file contains all of the input parameters that the user can specify when deploying this Terraform template. 23 24 