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 Terraform Cloud and Terraform Enterprise, the self-hosted distribution, to extend insight into dynamic updates of your network infrastructure.

FeaturesOpen SourceEnterprise
Consul NamespaceDefault namespace onlyFilter task triggers by any namespace
Automation DriverTerraform OSSTerraform OSS, Terraform Cloud, or Terraform Enterprise
Terraform WorkspacesLocalLocal workspaces with the Terraform driver or remote workspaces with the Terraform Cloud driver
Terraform Backend Optionsazurerm, consul, cos, gcs, kubernetes, local, manta, pg, and s3 with the Terraform driverThe supported backends for CTS with the Terraform driver or Terraform Cloud with the Terraform Cloud driver
Terraform VersionOne Terraform version for all tasksOptional Terraform version per task when using the Terraform Cloud driver
Terraform Run OutputCTS logsCTS logs or Terraform output organized by Terraform Cloud remote workspaces
Credentials and secretsOn disk as .tfvars files or in shell environmentSecured variables stored in remote workspace
AuditTerraform audit logs (Terraform Cloud or Terraform Enterprise)
CollaborationRun history, triggers, and notifications supported on Terraform Cloud
GovernanceSentinel to enforce governance policies as code

The Terraform Cloud driver enables CTS Enterprise to integrate with Terraform Cloud or Terraform Enterprise. The Terraform Cloud 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.