This release contains a major change to the behavior when updating tasks. In most cases, this change has no effect, but be aware of the change in behavior when omitting a revision of the task definition. In particular, if you are building a deployment workflow where the update timing of task definitions and the update timing of scheduled tasks are different, the revisions that are executed may be different.
- #57: Selective Updates (@HistoireDeBabar)
- Previously, Elastic Whenever recreates all scheduled tasks after deleting all tasks when updating tasks. However, in this case, there is a risk that frequently invoked tasks will not be executed, so this change now creates/deletes only those tasks that have changed.
- Due to this change, the naming convention for scheduled tasks has changed. When updating from v0.6, all rules will be deleted and recreated due to different naming conventions, and the behavior will be the same as before. After that, the task will not change if the names are the same.
- The breaking change is that the behavior when omitting a revision of a task definition has changed. Previously, when you created a task, you resolved the latest revision at that time, so even if the task definition was updated, the revision that was executed was always the same. In v0.7 and later, revisions are not resolved when you created a task, so the latest revision is always adopted.
- #51: Avoid hitting rate limits fetching credentials when running under ECS or with an IAM profile (@stevenwilliamson)
- #53: Migrate CI to GitHub Actions from Travis CI
- #42: Fix typo in clear task log line (@HistoireDeBabar)
- Retry for concurrent modification (#41)
- CI against Ruby 2.6 (#40)
Elastic Whenever now supports Fargate launch type. Thanks @avinson.
From this release, ECS parameters must be passed as arguments. Previously, it supported schedule file variables, but it will be ignored.
# Before
$ elastic_whenever --set 'cluster=ecs-test&task_definition=oneoff-application:2&container=oneoff'
# After
$ elastic_whenever --cluster ecs-test --task-definition oneoff-application:2 --container oneoff
- update elastic_whenever for FARGATE launch type (#34)
- fix:
Task::Role#exists?
always return true (#33)
- add
attr_reader :enviroment
(#32)