-
Notifications
You must be signed in to change notification settings - Fork 18
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
Chore: Update actions to v2 and assumed role #686
Conversation
Coverage of commit
|
Deploying to dev-green to double-check that it works. |
.github/workflows/deploy-prod.yml
Outdated
id: build-push | ||
with: | ||
aws-access-key-id: ${{ secrets.AWS_ACCESS_KEY_ID }} | ||
role-to-assume: ${{ secrets.AWS_ROLE_ARN }} | ||
aws-secret-access-key: ${{ secrets.AWS_SECRET_ACCESS_KEY }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
question: do you still need the secret key here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good catch, I do not!
Coverage of commit
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🍰
Summary of changes
Asana Ticket: Update application repos to use the new version of the GitHub action(s) (v2 tag)
This PR updates the deploy workflow to use v2 of the
build-push-ecr
anddeploy-ecs
actions. These updated actions assume an IAM role instead of relying on long-lasting AWS keys for an IAM user