Consul-Terraform-Sync Enterprise

Consul-Terraform-Sync (CTS) Enterprise is available with Consul Enterprise and requires a Consul license to be applied.

Enterprise features of CTS address organization complexities of collaboration, operations, scale, and governance. CTS Enterprise supports an official integration with HCP Terraform and Terraform Enterprise, the self-hosted distribution, to extend insight into dynamic updates of your network infrastructure.

Features	Community Edition	Enterprise
Consul Namespace	Default namespace only	Filter task triggers by any namespace
Automation Driver	Terraform Community Edition	Terraform Community Edition, HCP Terraform, or Terraform Enterprise
Terraform Workspaces	Local	Local workspaces with the Terraform driver or remote workspaces with the HCP Terraform driver
Terraform Backend Options	azurerm, consul, cos, gcs, kubernetes, local, manta, pg, and s3 with the Terraform driver	The supported backends for CTS with the Terraform driver or HCP Terraform with the HCP Terraform driver
Terraform Version	One Terraform version for all tasks	Optional Terraform version per task when using the HCP Terraform driver
Terraform Run Output	CTS logs	CTS logs or Terraform output organized by THCP Terraform remote workspaces
Credentials and secrets	On disk as `.tfvars` files or in shell environment	Secured variables stored in remote workspace
Audit		Terraform audit logs (HCP Terraform or Terraform Enterprise)
Collaboration		Run history, triggers, and notifications supported on HCP Terraform
Governance		Sentinel to enforce governance policies as code

The HCP Terraform driver enables CTS Enterprise to integrate with HCP Terraform or Terraform Enterprise. The HCP Terraform driver page provides an overview of how the integration works within CTS.

Consul Admin Partition Support

CTS subscribes to a Consul agent. Depending on the admin partition the Consul agent is a part of and the services within the admin partition, CTS will be able to subscribe to those services and support the automation workflow. As such, admin partitions are not relevant to the CTS workflow. We recommend deploying a single CTS instance that subscribes to services/KV within a single partition and using a different CTS instance (or instances) to subscribe to services/KV in another partition.