Skip to content

Releases: dflook/terraform-github-actions

v1.37.0

29 Oct 15:20
3cca384
Compare
Choose a tag to compare

All the terraform actions in this repository are released as one.
Use the actions as part of a GitHub Actions workflow, e.g:

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v3

    - uses: dflook/[email protected]
      with:
        path: my-terraform-config

You can specify an action version as:

  • @v1.37.0 to use exactly this release
  • @v1.37 to use the latest patch release for this specific minor version
  • @v1 to use the latest patch release for this specific major version

Changes

Added

v1.36.2

17 Aug 15:26
44035ba
Compare
Choose a tag to compare

All the terraform actions in this repository are released as one.
Use the actions as part of a GitHub Actions workflow, e.g:

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v3

    - uses: dflook/[email protected]
      with:
        path: my-terraform-config

You can specify an action version as:

  • @v1.36.2 to use exactly this release
  • @v1.36 to use the latest patch release for this specific minor version
  • @v1 to use the latest patch release for this specific major version

Changes

Fixed

  • When no terraform version is specified and no state file exists the actions will now use the latest terraform version, instead of incorrectly using Terraform 0.9.

v1.36.1

15 Jul 18:55
e9e3ddc
Compare
Choose a tag to compare

All the terraform actions in this repository are released as one.
Use the actions as part of a GitHub Actions workflow, e.g:

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v3

    - uses: dflook/[email protected]
      with:
        path: my-terraform-config

You can specify an action version as:

  • @v1.36.1 to use exactly this release
  • @v1.36 to use the latest patch release for this specific minor version
  • @v1 to use the latest patch release for this specific major version

Changes

Fixed

  • The selected workspace was not being shown in the workflow log when using a partial cloud block.

v1.36.0

27 Jun 17:13
48f4a12
Compare
Choose a tag to compare

All the terraform actions in this repository are released as one.
Use the actions as part of a GitHub Actions workflow, e.g:

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v3

    - uses: dflook/[email protected]
      with:
        path: my-terraform-config

You can specify an action version as:

  • @v1.36.0 to use exactly this release
  • @v1.36 to use the latest patch release for this specific minor version
  • @v1 to use the latest patch release for this specific major version

Changes

Added

  • Support for being triggered by repository_dispatch events.

    Previously dflook/terraform-plan and dflook/terraform-apply couldn't work with PR comments when triggered by repository_dispatch events. With this change repository_dispatch events that include the PR api url in the client payload will be able to use PR comments.

    The minimum client payload looks like:

    {
      "pull_request": {
        "url": "https://api.github.com/repos/dflook/terraform-github-actions/pulls/1"
      }
    }

v1.35.0

18 Jun 14:59
941c05e
Compare
Choose a tag to compare

All the terraform actions in this repository are released as one.
Use the actions as part of a GitHub Actions workflow, e.g:

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v3

    - uses: dflook/[email protected]
      with:
        path: my-terraform-config

You can specify an action version as:

  • @v1.35.0 to use exactly this release
  • @v1.35 to use the latest patch release for this specific minor version
  • @v1 to use the latest patch release for this specific major version

Changes

Added

  • Support for partial or empty cloud blocks. This means you can use a placeholder cloud block in your terraform, like so:
terraform {
  cloud {
  }
}

The configuration will be completed with the TF_CLOUD_ORGANIZATION and TF_CLOUD_HOSTNAME environment variables - the workspace should be specified using the workspace input.
As always, any tokens can be supplied in the TERRAFORM_CLOUD_TOKENS environment variable.

v1.34.0

10 Mar 17:31
2e81e39
Compare
Choose a tag to compare

All the terraform actions in this repository are released as one.
Use the actions as part of a GitHub Actions workflow, e.g:

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v3

    - uses: dflook/[email protected]
      with:
        path: my-terraform-config

You can specify an action version as:

  • @v1.34.0 to use exactly this release
  • @v1.34 to use the latest patch release for this specific minor version
  • @v1 to use the latest patch release for this specific major version

Changes

Added

  • The action image now also builds for arm64, meaning these actions will work on linux/arm64 runners.

Fixed

  • Workaround Terraform 1.4.0 sometimes forgetting to output anything.

v1.33.0

28 Feb 17:41
632d299
Compare
Choose a tag to compare

All the terraform actions in this repository are released as one.
Use the actions as part of a GitHub Actions workflow, e.g:

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v3

    - uses: dflook/[email protected]
      with:
        path: my-terraform-config

You can specify an action version as:

  • @v1.33.0 to use exactly this release
  • @v1.33 to use the latest patch release for this specific minor version
  • @v1 to use the latest patch release for this specific major version

Changes

Added

  • The dflook/terraform-plan and dflook/terraform-apply actions now have a destroy input.
    When setting destroy: true terraform will run in destroy mode, planning the destruction of all resources.
    This allows reviewing the effect of a destroy before applying it.

    The dflook/terraform-destroy action is unchanged and will still immediately destroy all resources.

v1.32.1

02 Feb 23:22
2dcb54f
Compare
Choose a tag to compare

All the terraform actions in this repository are released as one.
Use the actions as part of a GitHub Actions workflow, e.g:

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v3

    - uses: dflook/[email protected]
      with:
        path: my-terraform-config

You can specify an action version as:

  • @v1.32.1 to use exactly this release
  • @v1.32 to use the latest patch release for this specific minor version
  • @v1 to use the latest patch release for this specific major version

Changes

Fixed

  • When triggered by issue_comment or pull_request_review_comment events, the action will again add a 👍 reaction to the comment. This stopped working in v1.30.0

v1.32.0

28 Jan 13:47
a33aa1e
Compare
Choose a tag to compare

All the terraform actions in this repository are released as one.
Use the actions as part of a GitHub Actions workflow, e.g:

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v3

    - uses: dflook/[email protected]
      with:
        path: my-terraform-config

You can specify an action version as:

  • @v1.32.0 to use exactly this release
  • @v1.32 to use the latest patch release for this specific minor version
  • @v1 to use the latest patch release for this specific major version

Changes

Added

Changed

  • If a terraform operation fails because the state is locked the failure-reason output will now be set to state-locked, where before it may have been apply-failed or destroy-failed.

v1.31.1

01 Dec 09:36
d37748b
Compare
Choose a tag to compare

All the terraform actions in this repository are released as one.
Use the actions as part of a GitHub Actions workflow, e.g:

jobs:
  build:
    runs-on: ubuntu-latest
    steps:
    - uses: actions/checkout@v3

    - uses: dflook/[email protected]
      with:
        path: my-terraform-config

You can specify an action version as:

  • @v1.31.1 to use exactly this release
  • @v1.31 to use the latest patch release for this specific minor version
  • @v1 to use the latest patch release for this specific major version

Changes

Fixed

  • Failing to read backend config files for the purpose of identifying the backend state. This meant multiple plans with only
    different backend config files would overwrite each others PR comments.