bccd920db7
* updated docs - added docs for start command - deprecated running without a command - added instructions for autocomplete setup * addressed review comments * addressed review comments * addressed review comments * docs/nia: Terraform Cloud agent support - Add agent as a supported execution mode - Add terraform_cloud_workspace configuration - Deprecate existing terraform_version config * license block docs * added HCP Consul to compatibility * added HCP instructions * addressed review comments * added new auto-retrieval behavior to license docs * addressed review comments * addressed review comments * Apply suggestions from code review * Apply suggestions from code review * updated docs * updated docs * Apply suggestions from code review Co-authored-by: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com> * fixed heading types * fixed heading types * update docs * docs/nia: Add service registration configurations * docs/nia: Style guide updates * docs/nia: Update with beta docs feedback * docs/nia: Update license config formatting Other top-level blocks aren't included in the list of global config options, so removed the liciense entry. * docs/nia: Add auto-retrieval section to license page * docs/nia: Separate column for HCP Consul support * docs/nia: Compatiblity version upper bounds * docs/nia: Fix broken links * docs/nia: Style guide fixes Co-authored-by: Jeff Boruszak <104028618+boruszak@users.noreply.github.com> * Remove RequestId field from cts health api docs. * docs/nia - Update CTS service id format (#13125) * docs/nia: Convert Consul config to table format * docs/nia: Add ACL token policy requirements * update docs (#13174) * docs/nia: Fix ca_path, key default, and some links * docs/nia: Add CTS service address config * Update website/content/docs/nia/cli/index.mdx * docs/nia: update for 0.6 GA (#13191) Co-authored-by: devarshishah3 <devarshishah3@gmail.com> Co-authored-by: Michael Wilkerson <62034708+wilkermichael@users.noreply.github.com> Co-authored-by: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com> Co-authored-by: Melissa Kam <mkam@hashicorp.com> Co-authored-by: trujillo-adam <47586768+trujillo-adam@users.noreply.github.com> Co-authored-by: Melissa Kam <3768460+mkam@users.noreply.github.com> Co-authored-by: Jeff Boruszak <104028618+boruszak@users.noreply.github.com> Co-authored-by: Derek Menteer <derek.menteer@hashicorp.com> Co-authored-by: lornasong <lornasong@users.noreply.github.com> Co-authored-by: hashi-derek <105233703+hashi-derek@users.noreply.github.com> Co-authored-by: devarshishah3 <devarshishah3@gmail.com>
84 lines
5.1 KiB
Plaintext
84 lines
5.1 KiB
Plaintext
---
|
|
layout: docs
|
|
page_title: Consul-Terraform-Sync Enterprise License
|
|
description: >-
|
|
Consul-Terraform-Sync Enterprise License
|
|
---
|
|
|
|
# Consul-Terraform-Sync Enterprise License
|
|
|
|
<EnterpriseAlert>
|
|
Licenses are only required for Consul-Terraform-Sync (CTS) Enterprise
|
|
</EnterpriseAlert>
|
|
|
|
CTS Enterprise binaries require a [Consul Enterprise license](/docs/enterprise/license/overview) to run. There is no CTS Enterprise specific license. As a result, CTS Enterprise's licensing is very similar to Consul Enterprise.
|
|
|
|
All CTS Enterprise features are available with a valid Consul Enterprise license, regardless of your Consul Enterprise packaging or pricing model.
|
|
|
|
To get a trial license for CTS, you can sign-up for the [trial license for Consul Enterprise](/docs/enterprise/license/faq#q-where-can-users-get-a-trial-license-for-consul-enterprise).
|
|
|
|
## Automatic License Retrieval
|
|
CTS automatically retrieves a license from Consul on startup and then attempts to retrieve a new license once a day. If the current license is reaching its expiration date, CTS attempts to retrieve a license with increased frequency, as defined by the [License Expiration Date Handling](/docs/nia/enterprise/license#license-expiration-handling).
|
|
|
|
~> Enabling automatic license retrieval is recommended when using HCP Consul, as HCP Consul licenses expire more frequently than Consul Enterprise licenses. Without auto-retrieval enabled, you have to restart CTS every time you load a new license.
|
|
|
|
## Setting the License Manually
|
|
|
|
If a license needs to be manually set, choose one of the following methods (in order of precedence) to set the license:
|
|
|
|
1. Set the `CONSUL_LICENSE` environment variable to the license string.
|
|
|
|
```shell-session
|
|
export CONSUL_LICENSE=<LICENSE_VALUE>
|
|
```
|
|
|
|
1. Set the `CONSUL_LICENSE_PATH` environment variable to the path of the file containing the license.
|
|
|
|
```shell-session
|
|
export CONSUL_LICENSE_PATH=<PATH>/<TO>/<FILE>
|
|
```
|
|
|
|
1. To point to the file containing the license, in the configuration file, configure the [`license`](/docs/nia/configuration#license) path option.
|
|
|
|
```hcl
|
|
license {
|
|
path = "<PATH>/<TO>/<FILE>"
|
|
}
|
|
```
|
|
|
|
1. To point to the file containing the license, in the configuration file, configure the [`license_path`](/docs/nia/configuration#license_path) option i. **Deprecated in CTS 0.6.0 and will be removed in a future release. Use [license block](/docs/nia/configuration#license) instead.**
|
|
|
|
```hcl
|
|
license_path = "<PATH>/<TO>/<FILE>"
|
|
```
|
|
|
|
~> **Note**: the [options to set the license and the order of precedence](/docs/enterprise/license/overview#binaries-without-built-in-licenses) are the same as Consul Enterprise server agents.
|
|
Visit the [Enterprise License Tutorial](https://learn.hashicorp.com/tutorials/nomad/hashicorp-enterprise-license?in=consul/enterprise) for detailed steps on how to install the license key.
|
|
|
|
### Updating the License Manually
|
|
To update the license when it expires or is near the expiration date and automatic license retrieval is disabled:
|
|
|
|
1. Update the license environment variable or configuration with the new license value or path to the new license file
|
|
1. Stop and restart CTS Enterprise
|
|
|
|
Once CTS Enterprise starts again, it will pick up the new license and run the tasks with any changes that may have occurred between the stop and restart period.
|
|
|
|
## License Expiration Handling
|
|
|
|
Licenses have an expiration date and a termination date. The termination date is a time at or after the license expires. CTS Enterprise will cease to function once the termination date has passed.
|
|
|
|
The time between the expiration and termination dates is a grace period. Grace periods are generally 24-hours, but you should refer to your license agreement for complete terms of your grace period.
|
|
|
|
When approaching expiration and termination, by default, CTS Enterprise will attempt to retrieve a new license. If auto-retrieval is disabled, CTS Enterprise will provide notifications in the system logs:
|
|
|
|
| Time period | Behavior - auto-retrieval enabled (default) |Behavior - auto-retrieval disabled |
|
|
| ------------------------------------------- |-------------------------------------------- |---------------------------------- |
|
|
| 30 days before expiration | License retrieval attempt every 24-hours | Warning-level log every 24-hours |
|
|
| 7 days before expiration | License retrieval attempt every 1 hour | Warning-level log every 1 hour |
|
|
| 1 day before expiration | License retrieval attempt every 5 minutes | Warning-level log every 5 minutes |
|
|
| 1 hour before expiration | License retrieval attempt every 1 minute | Warning-level log every 1 minute |
|
|
| At or after expiration (before termination) | License retrieval attempt every 1 minute | Error-level log every 1 minute |
|
|
| At or after termination | Error-level log and exit | Error-level log and exit |
|
|
|
|
~> **Note**: Notification frequency and [grace period](/docs/enterprise/license/faq#q-is-there-a-grace-period-when-licenses-expire) behavior is the same as Consul Enterprise.
|