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

• container-definitions configuration is now optional (see #95) @toote

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