Getting set-output deprecation warning when running GHA pipelines.yml in ref arch

[umm0n]

We've started getting this warning when running our ref arch deployed pipelines.yml in Github Actions:

The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Is there an updated version of this pipelines.yml for GHA that implements this new schema? Where could we find it?

r:terraform-aws-ci

---

Tracked in ticket #109422

[umm0n]

For reference, this is the pipelines.yml we're using:

######################################################################################################################
# INFRASTRUCTURE CI/CD CONFIGURATION
#
# This configures GitHub Actions to implement a CI/CD pipeline for infrastructure code. Refer to the Gruntwork Production
# Deployment Guide, "How to configure a production-grade CI/CD workflow for infrastructure code"
# (https://gruntwork.io/guides/automations/how-to-configure-a-production-grade-ci-cd-setup-for-apps-and-infrastructure-code/)
# for details on how the pipeline is setup.
#
# The following pipeline is implemented in this configuration:
#
# - For any commit on any branch, detect all the terragrunt modules that changed between the `HEAD` of the branch and
#  `master` and run `terragrunt plan` on each of those modules.
# - For commits to `master`:
#     - Run `plan` as above, only instead of comparing the `HEAD` of the branch to `master`, this will only look at the
#       last commit that triggered the build. Note that this will include all the changes that were merged in from the
#       branch as the last commit is a merge commit containing all the changes.
#     - Hold for approval.
#     - If approved:
#         - Find all the build scripts that were changed and run them. This will create the necessary resources that are
#           not managed by Terraform, such as AMIs.
#         - Run `terragrunt apply` on each of the updated modules.
#
######################################################################################################################
name: gruntwork-pipelines
on:
  push:
    paths-ignore:
      - '.github/**'

env:
  GRUNTWORK_INSTALLER_VERSION: v0.0.38
  MODULE_CI_VERSION: v0.40.0
  MODULE_SECURITY_VERSION: v0.61.0
  # Disables the use of the Amazon EC2 instance metadata service (IMDS).
  # Forces the AWS CLI to use the env vars defined above for credentials.
  AWS_EC2_METADATA_DISABLED: true


jobs:
  plan_and_deploy:
    runs-on: ubuntu-20.04
    steps:
      - uses: actions/checkout@v3
        with:
          # Fetch all history
          fetch-depth: 0

      - name: Set custom ref variables
        id: ref
        run: |
          echo "::set-output name=source_ref::$(./.github/scripts/source-ref.sh)"
          echo "::set-output name=short_ref::${GITHUB_REF#refs/*/}"
        shell: bash

      - name: Install utilities
        run: ./_ci/scripts/install.sh
        shell: bash
        env:
          GITHUB_OAUTH_TOKEN: ${{ secrets.GH_TOKEN }}

      - name: Notify Slack of upcoming plan
        uses: slackapi/[email protected]
        with:
          payload: "{\"status\":\"Preparing to run plan.\",\"branch\":\"${{ steps.ref.outputs.short_ref }}\",\"repo\":\"${{ github.repository }}\",\"actor\":\"${{ github.actor }}\",\"url\":\"${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}\"}"
        env:
          SLACK_WEBHOOK_URL: ${{ secrets.SLACK_WEBHOOK_URL }}

      - name: run build scripts
        id: build-scripts
        run: ./_ci/scripts/run-build-scripts.sh "${{ steps.ref.outputs.source_ref }}" "${{ github.sha }}"
        shell: bash
        env:
          GITHUB_OAUTH_TOKEN: ${{ secrets.GH_TOKEN }}
          AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
          AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}

      - name: run plan
        id: plan
        run: ./_ci/scripts/deploy-infra.sh "${{ steps.ref.outputs.source_ref }}" "${{ github.sha }}" plan
        shell: bash
        env:
          GITHUB_OAUTH_TOKEN: ${{ secrets.GH_TOKEN }}
          AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
          AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}

      - name: Notify Slack of failed plan
        uses: slackapi/[email protected]
        if: failure() && steps.plan.outcome == 'failure'
        with:
          payload: "{\"status\":\"Plan failed.\",\"branch\":\"${{ steps.ref.outputs.short_ref }}\",\"repo\":\"${{ github.repository }}\",\"actor\":\"${{ github.actor }}\",\"url\":\"${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}\"}"
        env:
          SLACK_WEBHOOK_URL: ${{ secrets.SLACK_WEBHOOK_URL }}

      - name: Notify Slack of successful plan
        uses: slackapi/[email protected]
        if: success() && steps.plan.outcome == 'success'
        with:
          payload: "{\"status\":\"Plan successful!\",\"branch\":\"${{ steps.ref.outputs.short_ref }}\",\"repo\":\"${{ github.repository }}\",\"actor\":\"${{ github.actor }}\",\"url\":\"${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}\"}"
        env:
          SLACK_WEBHOOK_URL: ${{ secrets.SLACK_WEBHOOK_URL }}

      - name: Notify Slack of upcoming deploy
        uses: slackapi/[email protected]
        if: github.ref == 'refs/heads/master'
        with:
          payload: "{\"status\":\"Preparing to deploy.\",\"branch\":\"${{ steps.ref.outputs.short_ref }}\",\"repo\":\"${{ github.repository }}\",\"actor\":\"${{ github.actor }}\",\"url\":\"${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}\"}"
        env:
          SLACK_WEBHOOK_URL: ${{ secrets.SLACK_WEBHOOK_URL }}

      - name: run deploy
        id: deploy
        if: github.ref == 'refs/heads/master'
        run: ./_ci/scripts/deploy-infra.sh "${{ steps.ref.outputs.source_ref }}" "${{ steps.ref.outputs.short_ref }}" apply
        shell: bash
        env:
          GITHUB_OAUTH_TOKEN: ${{ secrets.GH_TOKEN }}
          AWS_ACCESS_KEY_ID: ${{ secrets.AWS_ACCESS_KEY_ID }}
          AWS_SECRET_ACCESS_KEY: ${{ secrets.AWS_SECRET_ACCESS_KEY }}

      - name: Notify Slack of failed deploy
        uses: slackapi/[email protected]
        if: github.ref == 'refs/heads/master' && failure() && steps.deploy.outcome == 'failure'
        with:
          payload: "{\"status\":\"Deploy failed.\",\"branch\":\"${{ steps.ref.outputs.short_ref }}\",\"repo\":\"${{ github.repository }}\",\"actor\":\"${{ github.actor }}\",\"url\":\"${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}\"}"
        env:
          SLACK_WEBHOOK_URL: ${{ secrets.SLACK_WEBHOOK_URL }}

      - name: Notify Slack of successful deploy
        uses: slackapi/[email protected]
        if: github.ref == 'refs/heads/master' && success() && steps.deploy.outcome == 'success'
        with:
          payload: "{\"status\":\"Deploy successful!\",\"branch\":\"${{ steps.ref.outputs.short_ref }}\",\"repo\":\"${{ github.repository }}\",\"actor\":\"${{ github.actor }}\",\"url\":\"${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}\"}"
        env:
          SLACK_WEBHOOK_URL: ${{ secrets.SLACK_WEBHOOK_URL }}

And this is the source-ref.sh script:

# This is used to determine what to use as the base comparison point for determining what modules to deploy. The logic
# is as follows:
#   - If we are on the master branch, the comparison is only the current commit.
#   - If we are not on master, the comparison is to the current state of the master branch.
if [[ "${GITHUB_REF##*/}" == "master" ]]; then
  echo 'HEAD^'
else
  echo 'origin/master'
fi

[zackproser]

Hi,

Thanks for opening this discussion. We're aware of this deprecation warning and are tracking it internally. We'll update this thread once we've released our new workflows.

[umm0n]

Great, thank you!