actions-marketplace-validations/Digital Studio Operations Terraform Action
Validate, Plan and Deploy Terraform Code
View on GitHubTrust Signals
- Scorecard Score
- not yet scored
- Maintenance Recency
- Stale
- License
- None
- Runtime
- Deprecated runtime
Inputs
| name | description | required | default |
|---|---|---|---|
| apply-on-default-branch-only | If this flag is set to false it will run terraform apply on any branch, if it's true only on the default branch, normally main/master | no | true |
| apply-on-pull-request | If this flag is set to true it will run terraform apply on the pull_request event, e.g. if you want to the run tests on the deployed infra | no | false |
| detect-drift | If this flag is set to true the terraform plan can have drift, which normally would return an exit code of 2, thus causing the action to fail. | no | false |
| github-token | Github Token should just generally be secrets.GITHUB_TOKEN | no | — |
| comment-prefix | This string will be added to comments before the output of the terraform plan|apply | no | — |
| terraform-output-as-comment | If set to true, the plan and apply outputs will be added as a comment to the pr | no | true |
| upgrade-on-init | If set to true, the terraform init will run with -upgrade flag | no | false |
| validate | If set to true, it will run terraform validate on the working-directory | no | true |
| working-directory | Directory for the Terraform files, if not specified it will run from current directory | no | — |
Outputs
| name | description |
|---|---|
| terraform-plan-exit-code | This is the output of the terraform plan command. Only set if detect-drift is set to true |