-
Notifications
You must be signed in to change notification settings - Fork 473
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
Convert to Actions #289
Convert to Actions #289
Conversation
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.
needs one tweak to the README
README.md
Outdated
|
||
ecs-deploy -c production1 -n doorman-api -i my.private.repo/doorman-api -e CI_TIMESTAMP | ||
ecs-deploy -c CLUSTERNAME -n SERVICENAME -i my.private.repo.com/frontend_container:latest -e CI_TIMESTAMP |
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.
If you're using the -e
option, you probably shouldn't supply a tag (e.g. latest
).
so that each task definition refers to a unique docker image/tag. This gives us the | ||
ability to revert/rollback changes by just selecting a previous task definition and | ||
updating the service. We plan to add a revert command/option to ecs-deploy to simplify this further. | ||
For example, we want to use a unique docker image/tag for each task definition. This |
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.
looks good
Changed (non-breaking)
Feature PR Checklist
test.bats
file)Release PR Checklist
ecs-deploy
scriptRelease _._._ - Summary of change
(using whateverthe new version number is, plus a succinct summary of what changed)