Releases: buildkite-plugins/ecs-deploy-buildkite-plugin
v3.0.0 (🎒 Preparations)
What's new: Major Release
This release changes the assumptions made by the plugin, in particular it should greatly increase compatibility with existing configurations (like fargate, multiple load balancers or target groups, etc). This reduces the scope of things the plugin tries to do that meant possible issues and complexity in configurations by delegating those tasks to tools better suited for them (IaC).
Breaking Change
- The plugin assumes
jq
tool is available now - Service to update must exist and be configured as desired to use this plugin (see #106)
The following options related to configuring the service have been removed:
+ deployment-config
+ desired-count
+ load-balancer-name
+ service-definition
+ target-container-name
+ target-port
+ target-group
Note that specifying service-definition
will cause the execution to fail, the rest will just cause a warning to be printed.
Major change
Instead of having the container definition as a file in the repository, it can be obtained off the existing task family specified if the configuration is not present. Note that it is likely that the option will be removed in the future
Bug fixes
region
is now respected in all commands to AWS (done in #106, but heavily based off #102 by @t1maccapp)
Non-functionality changes
- Add example for using this tool with Fargate by @patrobinson in #98
- Add example on how to set env vars by @patrobinson in #99
- Update buildkite plugin plugin-linter to v3.3.0 by @renovate in #103
- Update buildkite plugin plugin-tester to v1.1.1 by @renovate in #104
- Add Code of Conduct by @tomowatt in #105
Full Changelog: v2.1.0...v3.0.0
v2.1.0 (☁️ Cloudy Day)
v2.0.1 (🛫 Re:Invent prep)
v2.0.0 (🍏 Green Apple)
What's new
task-definition
was renamed tocontainer-definition
- added support for
task-definition
andservice-definition
parameters
All these changes should help move this plugin to better support Fargate. #77 @aleksclark / @toote
Upgrading
To upgrade, update your pipeline.yml
files:
steps:
- plugins:
- ecs-deploy#v1.4.1:
+ ecs-deploy#v2.0.0:
cluster: "my-ecs-cluster"
v1.5.0 (🌕 Full Moon)
Added
- Check container definition format (#45) @aleksclark / @toote
- Renovates Upgrades
Upgrading
To upgrade, update your pipeline.yml
files:
steps:
- plugins:
- ecs-deploy#v1.4.1:
+ ecs-deploy#v1.5.0:
cluster: "my-ecs-cluster"
v1.4.1 (Mischievous Mongoose)
Added
- Check container definition format (#45) @patrobinson
- Improve error messages
Upgrading
To upgrade, update your pipeline.yml
files:
steps:
- plugins:
- ecs-deploy#v1.4.0:
+ ecs-deploy#v1.4.1:
cluster: "my-ecs-cluster"
v1.4.0 (Calf Constraint)
Added
- Add option to pass region (#44) @patrobinson
Upgrading
To upgrade, update your pipeline.yml
files:
steps:
- plugins:
- ecs-deploy#v1.3.0:
+ ecs-deploy#v1.4.0:
cluster: "my-ecs-cluster"
v1.3.0 (🐮 Bull run)
Added
- Output service events when deploy fails and improve formatting (#38) @patrobinson
- Allow passing in execution role (#37) @patrobinson
- Add support for deployment configuration (#39) @patrobinson
- Improve README (#36) @patrobinson
Upgrading
To upgrade, update your pipeline.yml
files:
steps:
- plugins:
- ecs-deploy#v1.2.0:
+ ecs-deploy#v1.3.0:
cluster: "my-ecs-cluster"
v1.2.0 (🐓 Understated Chicken)
Added
- Support Classic Load Balancers (#32) @patrobinson
- Add support for multiple images in a single pipeline/definition (#33) @patrobinson
Upgrading
To upgrade, update your pipeline.yml
files:
steps:
- plugins:
- ecs-deploy#v1.1.0:
+ ecs-deploy#v1.2.0:
cluster: "my-ecs-cluster"
v1.1.0 (Mostly not useless)
Added
- Support ALBs (#31) @patrobinson
Fixed
- Ensure JQ starts at container definition key when dereferencing (#28) @patrobinson
Other changes
- Update buildkite plugin docker-compose to v3.0.3 (#30) @renovate
- Update buildkite plugin docker-compose to v3.0.2 (#29) @renovate
Upgrading
To upgrade, update your pipeline.yml
files:
steps:
- plugins:
- ecs-deploy#v1.0.0:
+ ecs-deploy#v1.1.0:
cluster: "my-ecs-cluster"