Terraform Cloud/Enterprise Provider

The official Terraform provider for Terraform Cloud/Enterprise.

As Terraform Enterprise is a self-hosted distribution of Terraform Cloud, this provider supports both Cloud and Enterprise use cases. In all/most documentation, the platform will always be stated as 'Terraform Enterprise' - but a feature will be explicitly noted as only supported in one or the other, if applicable (rare).

Note this provider is in beta and is subject to change (though it is generally quite stable). We will indicate any breaking changes by releasing new versions. Until the release of v1.0, any minor version changes will indicate possible breaking changes. Patch version changes will be used for both bugfixes and non-breaking changes.

• Documentation: https://registry.terraform.io/providers/hashicorp/tfe/latest/docs
• Website: https://registry.terraform.io/providers/hashicorp/tfe / https://www.terraform.io
• Discuss forum: https://discuss.hashicorp.com/c/terraform-providers

Installation

Declare the provider in your configuration and terraform init will automatically fetch and install the provider for you from the Terraform Registry:

terraform {
  required_providers {
    tfe = {
      version = "~> 0.30.2"
    }
  }
}

For production use, you should constrain the acceptable provider versions via configuration (as above), to ensure that new versions with breaking changes will not be automatically installed by terraform init in the future. As this provider is still at version zero, you should constrain the acceptable provider versions on the minor version.

The above snippet using required_providers is for Terraform 0.13+; if you are using Terraform version 0.12, you can constrain by adding the version constraint to the provider block instead:

provider "tfe" {
  version = "~> 0.30.2"
  ...
}

Since v0.24.0, this provider requires Terraform >= 0.12

For more information on provider installation and constraining provider versions, see the Provider Requirements documentation.

Usage

Create a user or team API token in Terraform Cloud/Enterprise, and use the token in the provider configuration block:

provider "tfe" {
  hostname = var.hostname # Optional, for use with Terraform Enterprise. Defaults to app.terraform.io.
  token    = var.token
}

# Create an organization
resource "tfe_organization" "org" {
  # ...
}

There are several other ways to configure the authentication token, depending on your use case. For other methods, see the Authentication documentation

For more information on configuring providers in general, see the Provider Configuration documentation.

Manually building the provider

You might prefer to manually build the provider yourself - perhaps access to the Terraform Registry or the official release binaries on releases.hashicorp.com are not available in your operating environment, or you're looking to contribute to the provider and are testing out a custom build.

Building the provider requires Go >= 1.16

Clone the repository, enter the directory, and build the provider:

$ git clone git@github.com:hashicorp/terraform-provider-tfe
$ cd terraform-provider-tfe
$ make build

This will build the provider and put the binary in the $GOPATH/bin directory. To use the compiled binary, you have several different options (this list is not exhaustive):

Using Terraform 0.13+

You can use a filesystem mirror (either one of the implied local mirror directories for your platform or by configuring your own).

See the Provider Requirements documentation for more information.

Using Terraform 0.12

• You can copy the provider binary to your ~/.terraform.d/plugins directory.
• You can create your test Terraform configurations in the same directory as your provider binary or you can copy the provider binary into the same directory as your test configurations.
• You can copy the provider binary into the same location as your terraform binary.

Contributing

Thanks for your interest in contributing; we appreciate your help! If you're unsure or afraid of anything, you can submit a work in progress (WIP) pull request, or file an issue with the parts you know. We'll do our best to guide you in the right direction, and let you know if there are guidelines we will need to follow. We want people to be able to participate without fear of doing the wrong thing.

👉 See Manually building the provider above.

Other helpful resources:

• Extending Terraform documentation
• Terraform Cloud API documentation
• Package documentation for the Terraform Cloud/Enterprise Go client (go-tfe)

Referencing a local version of go-tfe

You may want to create configs or run tests against a local version of go-tfe. Add the following line to go.mod above the require statement, using your local path to go-tfe:

replace github.com/hashicorp/go-tfe => /path-to-local-repo/go-tfe

Running the Linters Locally

1. Ensure you have installed golangci-lint
2. From the CLI, run golangci-lint run

Optionally, to integrate golangci-lint into your editor, see golangci-lint editor integration

Running the tests

See TESTS.md.

Updating the Changelog

Only update the Unreleased section. Make sure you change the unreleased tag to an appropriate version, using Semantic Versioning as a guideline.

Please use the template below when updating the changelog:

<change category>:
* **New Resource:** `name_of_new_resource` ([#123](link-to-PR))
* r/tfe_resource: description of change or bug fix ([#124](link-to-PR))

Updating the documentation

For pull requests that update provider documentation, please help us verify that the markdown will display correctly on the Registry:

• Copy the new markdown and paste it here to preview: https://registry.terraform.io/tools/doc-preview
• Paste a screenshot of that preview in your pull request.

Change categories

• BREAKING CHANGES: Use this for any changes that aren't backwards compatible. Include details on how to handle these changes.
• FEATURES: Use this for any large new features added.
• ENHANCEMENTS: Use this for smaller new features added.
• BUG FIXES: Use this for any bugs that were fixed.
• NOTES: Use this section if you need to include any additional notes on things like upgrading, upcoming deprecations, or any other information you might want to highlight.