Common problems with Terraform Cloud
When you add the integration
| What you see | What to do |
|---|---|
app.terraform.io refused the credentials (401). Check the token, and that it has not expired. Fix the field above, or save anyway if the source is only unreachable for now. | The token is wrong, expired or deleted. Create a new one: see Create a Terraform Cloud API token. |
On the Terraform tab of a component
| What you see | What to do |
|---|---|
| No Terraform tab | Add both the terraform/organization and terraform/workspaces annotations to the component, and turn on the Terraform plugin in Administration › Plugins. |
The workspace acme/shop-api cannot be reached with the Terraform token: check the terraform/organization and terraform/workspaces annotations, or the token access. | Check the organization and the workspace names in the annotations, and that the owner of the token can read this workspace in Terraform Cloud. |
When the tab says a module is missing
| What you see | What to do |
|---|---|
Astrolabe does not offer this Terraform feature on this instance. and A module is missing from this Astrolabe installation. Tell your Astrolabe administrator. | The integration may be connected and the plugin on, but this installation of Astrolabe lacks the module that serves Terraform. Tell your Astrolabe administrator. Nothing to change on the component. |
Not verified on an instance yet: this message needs an installation that lacks the module.
Still stuck?
Write to support@forgeit.fr with the name of the component and its Terraform Cloud workspace.