Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

maint: update AWS credendtials workflow step from v1 -> v4 #38

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

MikeGoldsmith
Copy link

Which problem is this PR solving?

Updates the AWS configure step used in the validate template workflow to use a newer version as v1 is now deprecated.

Short description of the changes

  • Update configure-aws-credentials step to use v4

How to verify that this has the expected result

The workflow can now complete as it's using a supported version.

@MikeGoldsmith MikeGoldsmith added the type: maintenance The necessary chores to keep the dust off. label Jun 11, 2024
@MikeGoldsmith MikeGoldsmith self-assigned this Jun 11, 2024
@MikeGoldsmith MikeGoldsmith requested a review from a team as a code owner June 11, 2024 12:53
@JamieDanielson JamieDanielson added the status: oncall Flagged for awareness from Honeycomb Telemetry Oncall label Jun 11, 2024
Copy link
Contributor

@JamieDanielson JamieDanielson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we also need to update this in the publish-templates.yaml workflow?

@dougireton
Copy link
Contributor

Maybe you want to update actions/checkout to v4 as well?

https://github.com/search?q=repo:honeycombio/cloudformation-integrations%20actions/checkout&type=code

@JamieDanielson
Copy link
Contributor

Hm, so it looks like the failed check from the other PR is actually on the publish-templates workflow based on the job action run - not the validate workflow. And I don't think it's because of the deprecated action. The failure is in Configure AWS Credentials, which includes a secret. The workflow sets pull_request, not pull_request_target. The main difference between the two is that the secrets are not passed to the runner when a workflow is triggered from a forked repository. So I think the failure would be resolved if someone with write access on this repo committed a change to trigger that workflow.

Either way it's probably worth updating these actions - but I don't think that is the primary issue causing the checks to fail on the other PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: oncall Flagged for awareness from Honeycomb Telemetry Oncall type: maintenance The necessary chores to keep the dust off.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants