merges with latest and adds GCP creds

Author: jackskj

CHANGELOG.md

@@ -0,0 +1,74 @@
+# Changelog
+
+## v0.6.2
+
+### Added
+
+* Added an `output` subcommand and corresponding `tf_actions_output` output.
+
+### Fixed
+
+* Fixed improper passing of arguments to the subcommand. ([#114](https://github.com/hashicorp/terraform-github-actions/issues/114))
+
+## v0.6.1
+
+### Fixed
+
+* Fixed improper handling of `args` in each `terraform` command when `args` contained no value. ([#109](https://github.com/hashicorp/terraform-github-actions/issues/109)) ([#110](https://github.com/hashicorp/terraform-github-actions/issues/110))
+
+## v0.6.0
+
+### Added
+
+* Allow passing arguments using GitHub Actions `args` attribute. ([#105](https://github.com/hashicorp/terraform-github-actions/issues/105))
+
+### Changed
+
+* Updated examples to reflect new additions.
+
+## v0.5.4
+
+### Changed
+
+* Always post a comment on a pull request regardless of exit code when using `apply`. ([#97](https://github.com/hashicorp/terraform-github-actions/issues/97))
+* Pass comment content to `jq` using pipes instead of arguments.
+
+## v0.5.3
+
+### Fixed
+
+* Fixed improper comment formatting on `fmt`, `plan`, and `apply`.
+
+## v0.5.2
+
+### Fixed
+
+* Fixed an error with `terraform fmt` processing STDERR output when `TF_LOG` was set.
+
+## v0.5.1
+
+### Fixed
+
+* Do not use `-recursive` option with `terraform fmt` for Terraform 0.11.x. ([#90](https://github.com/hashicorp/terraform-github-actions/issues/90))
+
+## v0.5.0
+
+### Added
+
+* Added new YAML syntax for GitHub Actions. 
+
+### Changed
+
+* Completely refactored the codebase into one GitHub Action. Please refer to the README for current usage.
+
+### Removed
+
+* Removed all `TF_ACTION` environment variables. Please refer to the README for current usage.
+* Removed HashiCorp Configuration Language (HCL) syntax.
+
+### Fixed
+
+* The actions now use the new YAML syntax. ([#67](https://github.com/hashicorp/terraform-github-actions/issues/67))
+* Added support for Terraform 0.11.14. ([#42](https://github.com/hashicorp/terraform-github-actions/issues/67))
+* Comments will not be posted to pull requests when `terraform plan` contains no changes. ([#29](https://github.com/hashicorp/terraform-github-actions/issues/67))
+* Added ability to specify a Terraform version to use. ([#23](https://github.com/hashicorp/terraform-github-actions/issues/67))

Dockerfile

@@ -0,0 +1,13 @@
+FROM alpine:3 
+
+RUN ["/bin/sh", "-c", "apk add --update --no-cache bash ca-certificates curl git jq openssh"]
+
+RUN ["bin/sh", "-c", "mkdir -p /src"]
+
+# ADDS GOOGLE CLOUD CREDENTIALS FILE 
+ENV GOOGLE_APPLICATION_CREDENTIALS /var/sec/gcp_cred.json
+RUN ["bin/sh", "-c", "echo $GOOGLE_CREDENTIALS > /var/sec/gcp_cred.json"]
+
+COPY ["src", "/src/"]
+
+ENTRYPOINT ["/src/main.sh"]

README.md

@@ -1,23 +1,106 @@
 # Terraform GitHub Actions
-These official Terraform GitHub Actions allow you to run `terraform fmt`, `validate`, `plan` and `apply` on your pull requests to help you review, validate and apply Terraform changes.
 
-## Getting Started
-To get started, check out our documentation: [https://www.terraform.io/docs/github-actions/getting-started/](https://www.terraform.io/docs/github-actions/getting-started/).
+Terraform GitHub Actions allow you to execute Terraform commands within GitHub Actions.
 
-## Actions
+The output of the actions can be viewed from the Actions tab in the main repository view. If the actions are executed on a pull request event, a comment may be posted on the pull request.
 
-### Fmt Action
-Runs `terraform fmt` and comments back if any files are not formatted correctly.
-<img src="./assets/fmt.png" alt="Terraform Fmt Action" width="80%" />
+Terraform GitHub Actions are a single GitHub Action that executes different Terraform subcommands depending on the content of the GitHub Actions YAML file.
 
-### Validate Action
-Runs `terraform validate` and comments back on error.
-<img src="./assets/validate.png" alt="Terraform Validate Action" width="80%" />
+## Success Criteria
 
-### Plan Action
-Runs `terraform plan` and comments back with the output.
-<img src="./assets/plan.png" alt="Terraform Plan Action" width="80%" />
+An exit code of `0` is considered a successful execution.
 
-### Apply Action
-Runs `terraform apply` and comments back with the output.
-<img src="./assets/apply.png" alt="Terraform Apply Action" width="80%" />
+## Usage
+
+The most common workflow is to run `terraform fmt`, `terraform init`, `terraform validate`, and `terraform plan` on all of the Terraform files in the root of the repository when a pull request is opened or updated. A comment will be posted to the pull request depending on the output of the Terraform subcommand being executed. This workflow can be configured by adding the following content to the GitHub Actions workflow YAML file.
+
+```yaml
+name: 'Terraform GitHub Actions'
+on:
+  - pull_request
+jobs:
+  terraform:
+    name: 'Terraform'
+    runs-on: ubuntu-latest
+    steps:
+      - name: 'Checkout'
+        uses: actions/checkout@master
+      - name: 'Terraform Format'
+        uses: hashicorp/terraform-github-actions@master
+        with:
+          tf_actions_version: 0.12.13
+          tf_actions_subcommand: 'fmt'
+          tf_actions_working_dir: '.'
+          tf_actions_comment: true
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+      - name: 'Terraform Init'
+        uses: hashicorp/terraform-github-actions@master
+        with:
+          tf_actions_version: 0.12.13
+          tf_actions_subcommand: 'init'
+          tf_actions_working_dir: '.'
+          tf_actions_comment: true
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+      - name: 'Terraform Validate'
+        uses: hashicorp/terraform-github-actions@master
+        with:
+          tf_actions_version: 0.12.13
+          tf_actions_subcommand: 'validate'
+          tf_actions_working_dir: '.'
+          tf_actions_comment: true
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+      - name: 'Terraform Plan'
+        uses: hashicorp/terraform-github-actions@master
+        with:
+          tf_actions_version: 0.12.13
+          tf_actions_subcommand: 'plan'
+          tf_actions_working_dir: '.'
+          tf_actions_comment: true
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+```
+
+This was a simplified example showing the basic features of these Terraform GitHub Actions. Please refer to the examples within the `examples` directory for other common workflows.
+
+## Inputs
+
+Inputs configure Terraform GitHub Actions to perform different actions.
+
+* `tf_actions_version` - (Required) The Terraform version to install and execute.
+* `tf_actions_subcommand` - (Required) The Terraform subcommand to execute. Valid values are `fmt`, `init`, `validate`, `plan`, and `apply`.
+* `tf_actions_working_dir` - (Optional) The working directory to change into before executing Terraform subcommands. Defaults to `.` which means use the root of the GitHub repository.
+* `tf_actions_comment` - (Optional) Whether or not to comment on GitHub pull requests. Defaults to `true`.
+
+## Outputs
+
+Outputs are used to pass information to subsequent GitHub Actions steps.
+
+* `tf_actions_plan_has_changes` - Whether or not the Terraform plan contained changes.
+* `tf_actions_output` - The Terraform outputs in JSON format.
+
+## Secrets
+
+Secrets are similar to inputs except that they are encrypted and only used by GitHub Actions. It's a convenient way to keep sensitive data out of the GitHub Actions workflow YAML file.
+
+* `GITHUB_TOKEN` - (Optional) The GitHub API token used to post comments to pull requests. Not required if the `tf_actions_comment` input is set to `false`.
+
+Other secrets may be needed to authenticate with Terraform backends and providers.
+
+**WARNING:** These secrets could be exposed if the action is executed on a malicious Terraform file. To avoid this, it is recommended not to use these Terraform GitHub Actions on repositories where untrusted users can submit pull requests.
+
+## Environment Variables
+
+Environment variables are exported in the environment where the Terraform GitHub Actions are executed. This allows a user to modify the behavior of certain GitHub Actions.
+
+The usual [Terraform environment variables](https://www.terraform.io/docs/commands/environment-variables.html) are supported. Here are a few of the more commonly used environment variables.
+
+* [`TF_LOG`](https://www.terraform.io/docs/commands/environment-variables.html#tf_log)
+* [`TF_VAR_name`](https://www.terraform.io/docs/commands/environment-variables.html#tf_var_name)
+* [`TF_CLI_ARGS`](https://www.terraform.io/docs/commands/environment-variables.html#tf_cli_args-and-tf_cli_args_name)
+* [`TF_CLI_ARGS_name`](https://www.terraform.io/docs/commands/environment-variables.html#tf_cli_args-and-tf_cli_args_name)
+* `TF_WORKSPACE`
+
+Other environment variables may be configured to pass data into Terraform. If the data is sensitive, consider using [secrets](#secrets) instead.

action.yml

@@ -0,0 +1,27 @@
+name: 'Terraform GitHub Actions'
+description: 'Runs Terraform commands via GitHub Actions.'
+author: 'HashiCorp, Inc. Terraform Team <[email protected]>'
+branding:
+  icon: 'terminal'
+  color: 'purple'
+inputs:
+  tf_actions_version:
+    description: 'Terraform version to install.'
+    required: true
+  tf_actions_subcommand:
+    description: 'Terraform subcommand to execute.'
+    required: true
+  tf_actions_working_dir:
+    description: 'Terraform working directory.'
+    default: '.'
+  tf_actions_comment:
+    description: 'Whether or not to comment on pull requests.'
+    default: true
+outputs:
+  tf_actions_plan_has_changes:
+    description: 'Whether or not the Terraform plan contained changes.'
+  tf_actions_output:
+    description: 'The Terraform outputs in JSON format.'
+runs:
+  using: 'docker'
+  image: './Dockerfile'