hcp-consul
hashicorp/hcp-consul/azurerm
Terraform module for HCP Consul on Azure
HCP Consul on Azure Module Terraform module for connecting a HashiCorp Cloud Platform (HCP) Consul cluster to Azure. Usage This module connects a HashiCorp Virtual Network (HVN) with an Azure VNet, ensuring that all networking rules are in place to allow a Consul client to communicate with the HCP Consul servers. The module accomplishes this in by: 1. Create and accept a peering connection between the HVN and VNet 2. Create HVN routes that will direct HCP traffic to the CIDR ranges of the subnets. 3. Create Azure ingress rules necessary for HCP Consul to communicate to Consul clients. Examples These examples allow you to easily research and demo HCP Consul. - hcp-vm-demo - Use Azure virtual machines to run Consul clients - hcp-aks-demo - Use an AKS cluster to deploy Consul clients License
| Name | Type | Description | Default |
|---|---|---|---|
| subnet_ids | list(string) | The subnets associated with the vnet | |
| vnet_id | string | the id of the vnet | |
| vnet_rg | string | The name of the vnet's resource group that everything will be created in | |
| tenant_id | string | this is tenant id | |
| subscription_id | string | this is the azure subscription id | |
| hvn | object({ hvn_id = stri | The HCP HVN to connect to the VPC as defined in the datasource for hcp_hvn | |
| security_group_names | list(string) | A list of security group IDs which should allow inbound Consul client traffic. I | [] |
| prefix | string | A prefix to be added to all resources to force uniqueness if required | "peering" |
nsg — Newly created azure nsg if 'security_group_names' was not providedAzure landing zones Terraform module
Terraform supermodule for the Terraform platform engineering for Azure
Terraform module to deploy landing zone subscriptions (and much more) in Azure
Terraform Module to define a consistent naming convention by (namespace, stage,