2020-04-23 12:57:44 -04:00
# setup-terraform
< p align = "left" >
< a href = "https://github.com/hashicorp/setup-terraform/actions" > < img alt = "Continuous Integration" src = "https://github.com/hashicorp/setup-terraform/workflows/Continuous%20Integration/badge.svg" / > < / a >
< a href = "https://github.com/hashicorp/setup-terraform/actions" > < img alt = "Setup Terraform" src = "https://github.com/hashicorp/setup-terraform/workflows/Setup%20Terraform/badge.svg" / > < / a >
< / p >
2020-05-05 19:46:33 -04:00
The `hashicorp/setup-terraform` action is a JavaScript action that sets up Terraform CLI in your GitHub Actions workflow by:
2020-04-23 12:57:44 -04:00
- Downloading a specific version of Terraform CLI and adding it to the `PATH` .
2020-09-17 09:59:58 -04:00
- Configuring the [Terraform CLI configuration file ](https://www.terraform.io/docs/commands/cli-config.html ) with a Terraform Cloud/Enterprise hostname and API token.
2020-05-05 19:46:33 -04:00
- Installing a wrapper script to wrap subsequent calls of the `terraform` binary and expose its STDOUT, STDERR, and exit code as outputs named `stdout` , `stderr` , and `exitcode` respectively. (This can be optionally skipped if subsequent steps in the same job do not need to access the results of Terraform commands.)
After you've used the action, subsequent steps in the same job can run arbitrary Terraform commands using [the GitHub Actions `run` syntax ](https://help.github.com/en/actions/reference/workflow-syntax-for-github-actions#jobsjob_idstepsrun ). This allows most Terraform commands to work exactly like they do on your local command line.
2020-04-23 12:57:44 -04:00
## Usage
This action can be run on `ubuntu-latest` , `windows-latest` , and `macos-latest` GitHub Actions runners. When running on `windows-latest` the shell should be set to Bash.
2020-05-06 22:45:26 -04:00
The default configuration installs the latest version of Terraform CLI and installs the wrapper script to wrap subsequent calls to the `terraform` binary.
2020-04-23 12:57:44 -04:00
```yaml
steps:
2020-05-15 13:27:42 -04:00
- uses: hashicorp/setup-terraform@v1
2020-04-23 12:57:44 -04:00
```
A specific version of Terraform CLI can be installed.
```yaml
steps:
2020-05-15 13:27:42 -04:00
- uses: hashicorp/setup-terraform@v1
2020-04-23 12:57:44 -04:00
with:
2020-05-14 22:41:26 -04:00
terraform_version: 0.12.25
2020-04-23 12:57:44 -04:00
```
Credentials for Terraform Cloud (app.terraform.io) can be configured.
```yaml
steps:
2020-05-15 13:27:42 -04:00
- uses: hashicorp/setup-terraform@v1
2020-04-23 12:57:44 -04:00
with:
cli_config_credentials_token: ${{ secrets.TF_API_TOKEN }}
```
Credentials for Terraform Enterprise can be configured.
```yaml
steps:
2020-05-15 13:27:42 -04:00
- uses: hashicorp/setup-terraform@v1
2020-04-23 12:57:44 -04:00
with:
cli_config_credentials_hostname: 'terraform.example.com'
cli_config_credentials_token: ${{ secrets.TF_API_TOKEN }}
```
2020-05-05 19:46:33 -04:00
The wrapper script installation can be skipped.
2020-04-23 12:57:44 -04:00
```yaml
steps:
2020-05-15 13:27:42 -04:00
- uses: hashicorp/setup-terraform@v1
2020-04-23 12:57:44 -04:00
with:
terraform_wrapper: false
```
2020-05-05 19:46:33 -04:00
Subsequent steps can access outputs when the wrapper script is installed.
2020-04-23 12:57:44 -04:00
```yaml
steps:
- uses: hashicorp/setup-terraform@v1
- run: terraform init
- id: plan
run: terraform plan -no-color
- run: echo ${{ steps.plan.outputs.stdout }}
- run: echo ${{ steps.plan.outputs.stderr }}
- run: echo ${{ steps.plan.outputs.exitcode }}
```
2020-05-05 19:46:33 -04:00
Outputs can be used in subsequent steps to comment on the pull request:
2020-04-23 12:57:44 -04:00
```yaml
2020-05-21 10:36:02 -04:00
defaults:
run:
working-directory: ${{ env.tf_actions_working_dir }}
2020-04-23 12:57:44 -04:00
steps:
2020-05-21 10:36:02 -04:00
- uses: actions/checkout@v2
2020-04-23 12:57:44 -04:00
- uses: hashicorp/setup-terraform@v1
2020-05-21 10:36:02 -04:00
- name: Terraform fmt
id: fmt
2020-09-09 02:50:49 +09:00
run: terraform fmt -check
2020-05-21 10:36:02 -04:00
continue-on-error: true
2020-04-23 12:57:44 -04:00
2020-05-21 10:36:02 -04:00
- name: Terraform Init
id: init
run: terraform init
- name: Terraform Validate
id: validate
run: terraform validate -no-color
- name: Terraform Plan
id: plan
2020-04-23 12:57:44 -04:00
run: terraform plan -no-color
2020-05-21 10:36:02 -04:00
continue-on-error: true
2020-04-23 12:57:44 -04:00
2022-03-04 09:36:33 +09:00
- uses: actions/github-script@v5
2020-04-23 12:57:44 -04:00
if: github.event_name == 'pull_request'
env:
2020-05-21 10:36:02 -04:00
PLAN: "terraform\n${{ steps.plan.outputs.stdout }}"
2020-04-23 12:57:44 -04:00
with:
github-token: ${{ secrets.GITHUB_TOKEN }}
script: |
2020-05-21 10:36:02 -04:00
const output = `#### Terraform Format and Style 🖌\` ${{ steps.fmt.outcome }}\`
#### Terraform Initialization ⚙️\`${{ steps.init.outcome }}\`
2021-05-13 18:20:26 -04:00
#### Terraform Validation 🤖\`${{ steps.validate.outputs.stdout }}\`
2020-05-21 10:36:02 -04:00
#### Terraform Plan 📖\`${{ steps.plan.outcome }}\`
< details > < summary > Show Plan< / summary >
2021-05-13 18:20:26 -04:00
\`\`\`\n
${process.env.PLAN}
\`\`\`
2020-05-21 10:36:02 -04:00
< / details >
*Pusher: @${{ github.actor }}, Action: \`${{ github.event_name }}\`, Working Directory: \`${{ env.tf_actions_working_dir }}\`, Workflow: \`${{ github.workflow }}\`* `;
2022-03-04 09:36:33 +09:00
github.rest.issues.createComment({
2020-04-23 12:57:44 -04:00
issue_number: context.issue.number,
owner: context.repo.owner,
repo: context.repo.repo,
2020-05-15 13:27:42 -04:00
body: output
2020-04-23 12:57:44 -04:00
})
```
## Inputs
2020-09-08 16:18:09 +02:00
The action supports the following inputs:
2020-04-23 12:57:44 -04:00
2020-09-08 16:18:09 +02:00
- `cli_config_credentials_hostname` - (optional) The hostname of a Terraform Cloud/Enterprise instance to
place within the credentials block of the Terraform CLI configuration file. Defaults to `app.terraform.io` .
2020-04-23 12:57:44 -04:00
2020-09-08 16:18:09 +02:00
- `cli_config_credentials_token` - (optional) The API token for a Terraform Cloud/Enterprise instance to
place within the credentials block of the Terraform CLI configuration file.
2020-04-23 12:57:44 -04:00
2020-09-08 16:18:09 +02:00
- `terraform_version` - (optional) The version of Terraform CLI to install. Instead of a full version string,
you can also specify a constraint string (see [Semver Ranges ](https://www.npmjs.com/package/semver#ranges )
2020-11-06 10:57:38 +11:00
for available range specifications). Examples are: `<0.14.0` , `~0.13.0` , `0.13.x` (all three installing
2020-12-08 11:26:01 -08:00
the latest available 0.13 version). Prerelease versions can be specified and a range will stay within the
given tag such as `beta` or `rc` . If no version is given, it will default to `latest` .
2020-09-08 16:18:09 +02:00
- `terraform_wrapper` - (optional) Whether to install a wrapper to wrap subsequent calls of
the `terraform` binary and expose its STDOUT, STDERR, and exit code as outputs
named `stdout` , `stderr` , and `exitcode` respectively. Defaults to `true` .
2020-04-23 12:57:44 -04:00
## Outputs
2020-09-08 16:18:09 +02:00
This action does not configure any outputs directly. However, when you set the `terraform_wrapper` input
to `true` , the following outputs is available for subsequent steps that call the `terraform` binary.
2020-04-23 12:57:44 -04:00
2020-05-15 13:27:42 -04:00
- `stdout` - The STDOUT stream of the call to the `terraform` binary.
2020-04-23 12:57:44 -04:00
2020-05-15 13:27:42 -04:00
- `stderr` - The STDERR stream of the call to the `terraform` binary.
2020-04-23 12:57:44 -04:00
2020-05-15 13:27:42 -04:00
- `exitcode` - The exit code of the call to the `terraform` binary.
2020-04-23 12:57:44 -04:00
## License
[Mozilla Public License v2.0 ](https://github.com/hashicorp/setup-terraform/blob/master/LICENSE )
## Code of Conduct
[Code of Conduct ](https://github.com/hashicorp/setup-terraform/blob/master/CODE_OF_CONDUCT.md )
2020-10-27 15:33:24 -04:00
## Experimental Status
By using the software in this repository (the "Software"), you acknowledge that: (1) the Software is still in development, may change, and has not been released as a commercial product by HashiCorp and is not currently supported in any way by HashiCorp; (2) the Software is provided on an "as-is" basis, and may include bugs, errors, or other issues; (3) the Software is NOT INTENDED FOR PRODUCTION USE, use of the Software may result in unexpected results, loss of data, or other unexpected results, and HashiCorp disclaims any and all liability resulting from use of the Software; and (4) HashiCorp reserves all rights to make all decisions about the features, functionality and commercial release (or non-release) of the Software, at any time and without any obligation or liability whatsoever.