#github-actions - May 2024

Artifact Attestations public beta
Artifact Attestations public beta
The post Artifact Attestations public beta appeared first on The GitHub Blog.

Dependabot pull requests jobs are now available to run on self hosted Actions runners
Dependabot pull requests jobs are now available to run on self hosted Actions runners
The post Dependabot pull requests jobs are now available to run on self hosted Actions runners appeared first on The GitHub Blog.

Actions: New region support for Azure private networking
Actions: New region support for Azure private networking
The post Actions: New region support for Azure private networking appeared first on The GitHub Blog.

Gah! just give me folder support for my workflows already....

GitHub-hosted runners: Public Beta of Ubuntu 24.04 is now available
GitHub-hosted runners: Public Beta of Ubuntu 24.04 is now available
The post GitHub-hosted runners: Public Beta of Ubuntu 24.04 is now available appeared first on The GitHub Blog.

Hi everybody 👋 new in the community, I was making a github action workflow that executes playwright tests, but then we realized that some of the endpoints are not exposed to internet, so my challenge now is to make a workflow_dispatch in github action that can trigger a workflow in AWS codepipeline (because here the endpoints are accessible), for that also I need to send some env variables declared in the workflow to codepipeline, have you guys done something like that? any document I can read to get more insights on how to achieve my goal?

New dates for Actions larger runner multi-label deprecation
New dates for Actions larger runner multi-label deprecation
The post New dates for Actions larger runner multi-label deprecation appeared first on The GitHub Blog.

Updated dates for Actions runner using Node20 instead of Node16 by default
Updated dates for Actions runner using Node20 instead of Node16 by default
The post Updated dates for Actions runner using Node20 instead of Node16 by default appeared first on The GitHub Blog.

Actions: Upcoming changes to GitHub-hosted macOS runners
Actions: Upcoming changes to GitHub-hosted macOS runners
The post Actions: Upcoming changes to GitHub-hosted macOS runners appeared first on The GitHub Blog.

Anyone facing issues with Affected Stacks, seems like it is unable to get the correct componentPath, runs previously successful are failing now:
Previously:

Run set +e
  set +e
  
  TERRAFORM_OUTPUT_FILE="./terraform-${GITHUB_RUN_ID}-output.txt"
  
  tfcmt \
  --config /home/runner/work/_actions/cloudposse/github-action-atmos-terraform-plan/v2/config/summary.yaml \
  -owner "Org" \
  -repo "aws_infra_atmos" \
  -var "target:ops-logging-deploy-org_vpc_logs-bucket" \
  -var "component:org_vpc_logs-bucket" \
  -var "componentPath:components/terraform/s3-bucket" \

Now:

Run set +e
  set +e
  
  TERRAFORM_OUTPUT_FILE="./terraform-${GITHUB_RUN_ID}-output.txt"
  
  tfcmt \
  --config /home/runner/work/_actions/cloudposse/github-action-atmos-terraform-plan/v2/config/summary.yaml \
  -owner "Org" \
  -repo "aws_infra_atmos" \
  -var "target:ops-logging-deploy-org_vpc_logs-bucket" \
  -var "component:org_vpc_logs-bucket" \
  -var "componentPath:components/terraform/" \

Which eventually leads to failure
This is my step snippet:

      - name: Plan Atmos Component
        uses: cloudposse/github-action-atmos-terraform-plan@v2
        with:
          component: ${{ matrix.component }}
          stack: ${{ matrix.stack }}
          atmos-config-path: /home/runner/work/_temp/atmos-config