-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add build-image.yml deployment workflow for the docker image #18
Conversation
This is almost the same deployment workflow we use in data-pipelines repository to build, tag and push the image to ECR: https://github.com/iFixit/data-pipelines/blob/main/.github/workflows/build-image.yml Saved the `role-to-assume` value in repository variables in the repo.
deploy_block 🚛 on #17 going out first |
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.
For added security we should use a secret instead of a variable for the IAM role arn.
@djmetzle is there anything else you can think of to make this workflow more secure?
We don't want to trigger the deployment workflow for security reasons.
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.
CR 👍 and un_dev_block ⚡
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.
un_deploy_block 👍 #17 has been merged
Summary
This is almost the same deployment workflow we use in
data-pipelines
repository to build,tag, and push the image to ECR:
https://github.com/iFixit/data-pipelines/blob/main/.github/workflows/build-image.yml
Saved the
role-to-assume
value in the secrets.QA notes
We probably have to merge this to test it (not really sure how to test without merging it).
qa_req 0
closes #15