#github-actions (2023-02)

Discussions related to GitHub Actions

2023-02-01

jose.amengual avatar
jose.amengual

is it possible with this : https://github.com/aws-actions/configure-aws-credentials or another action using OIDC to assume a role chaining? like assume a cicd role in the CICD account and then assume a rile int he dev account?

aws-actions/configure-aws-credentials

Configure AWS credential environment variables for use in other GitHub Actions.

Darren Cunningham avatar
Darren Cunningham

yes, I’ve done just that w/that action though I don’t have the workflow in hand

aws-actions/configure-aws-credentials

Configure AWS credential environment variables for use in other GitHub Actions.

jose.amengual avatar
jose.amengual

ok, I will give it a try, I think I will need to do some STS after

Darren Cunningham avatar
Darren Cunningham

from what I recall, I called the action twice. I wasn’t able to consolidate into a single call

1
jose.amengual avatar
jose.amengual

ahhh, using the session name from. the previous one

2023-02-23

johncblandii avatar
johncblandii

I found the docker build workflow in the registry (was good to see CP pop up there when searching).

I get this log when using it, though. Is this a familiar error?
Retrieving registries data through AWS SDK…
AWS ECR detected with us-east-1 region
Logging into https://123456789.dkr.ecr.us-east-1.amazonaws.com
Error: Error saving credentials: error storing credentials - err: exit status 1, out: not implemented

johncblandii avatar
johncblandii
      - name: Build
        id: build
        uses: cloudposse/github-action-docker-build-push@main
        with:
          registry: "${{ env.ECR_REGISTRY }}"
          organization: "${{ github.event.repository.owner.login }}"
          repository: "${{ env.ECR_REPOSITORY }}"

    outputs:
      image: ${{ steps.build.outputs.image }}
      tag: ${{ steps.build.outputs.tag }}
johncblandii avatar
johncblandii

oh and this is from a private github runner

johncblandii avatar
johncblandii
#29 Warning: The `set-output` command is deprecated and will be disabled soon.

Found a bug? Maybe our Slack Community can help.

Slack Community

Describe the Bug

Warning: 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/

Expected Behavior

No warning.

Steps to Reproduce

Steps to reproduce the behavior:

  1. Run the workflow

Screenshots

If applicable, add screenshots or logs to help explain your problem.

Environment (please complete the following information):

Anything that will help us triage the bug will help. Here are some ideas:

• OS: [e.g. Linux, OSX, WSL, etc] • Version [e.g. 10.15]

Additional Context

Add any other context about the problem here.

Erik Osterman (Cloud Posse) avatar
Erik Osterman (Cloud Posse)

yes, @Igor Rodionov will be working to fix these, but it may be a couple weeks

#29 Warning: The `set-output` command is deprecated and will be disabled soon.

Found a bug? Maybe our Slack Community can help.

Slack Community

Describe the Bug

Warning: 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/

Expected Behavior

No warning.

Steps to Reproduce

Steps to reproduce the behavior:

  1. Run the workflow

Screenshots

If applicable, add screenshots or logs to help explain your problem.

Environment (please complete the following information):

Anything that will help us triage the bug will help. Here are some ideas:

• OS: [e.g. Linux, OSX, WSL, etc] • Version [e.g. 10.15]

Additional Context

Add any other context about the problem here.

1
    keyboard_arrow_up