cultureamp / aws-assume-role-buildkite-plugin Goto Github PK

Hi team, love your work!

Found a usecase that I am having repeated where we need to assume a role, then revert, in order to upload artifacts.

For example:

• part 1: (optional) use original role (for example, download artifact previously uploaded)
• part 2: run command in assumed role (for example, cross account terraform planning or deployment to a remote end point of an S3 static website from a build artifact archive)
• part 3: revert to original role in order to upload artifact

Thoughts?

I have configured the steps where plugins listed in order

  - cultureamp/aws-assume-role#v0.1.0:
      role: "arn:aws:iam::1111111111111:role/buildkite-roles"
  - seek-oss/aws-sm#v2.2.1:
      env:
        GITHUB_TOKEN:
          secret-id: "buildkite-secret"
          json-key: ".github_token"

According to the documentation the plugins order of execution is based on the hooks defind here

Since the plugin cultureamp/aws-assume-role#v0.1.0 hook does not have a definition for environment, the secrets-manager's plugin hooks run before the aws-assume-role plugin's hook. due to which the pipeline job fails since agent underlying role does not access to secrets-manager.

Any suggestions would help.

Hi there!

We're using the v0.1.0 tag for our builds, and it looks like there has been a substantial amount of development on the plugin since then.

Would it be possible to tag a more recent version so we can have something newer (but not ever shifting) ?

Thanks very much