Merge pull request #104 from WilboMo/changelog

Metadata for v0.2.0

Author: WilboMo

CHANGELOG.md

@@ -1,3 +1,11 @@
+# 0.2.0
+
+* Add support for clusters larger than 50 container instances.
+* Add after-action summary and done message to log output.
+* Add check to reduce the chance of concurrent runs.
+
+Note: In the Bottlerocket ECS updater v0.1.0 release, support for clusters was limited to 50 container instances. In this release, clusters larger than 50 container instances are now supported. :tada: 
+
 # 0.1.0
 
 Initial release of the **Bottlerocket ECS updater** - A service to automatically manage Bottlerocket updates in an Amazon ECS cluster.

README.md

@@ -152,9 +152,6 @@ A container instance may be skipped for update when:
   The Bottlerocket ECS Updater uses newer [`apiclient update` commands](https://github.com/bottlerocket-os/bottlerocket#update-api) that were added in version [1.0.5](https://github.com/bottlerocket-os/bottlerocket/blob/develop/CHANGELOG.md#v105-2021-01-15).
   The SSM commands will fail if your Bottlerocket OS version is less than 1.0.5.
   Instances running Bottlerocket versions less than 1.0.5 need to be manually updated.
-* _Too many instances are in the cluster._
-  The Bottlerocket ECS Updater currently supports clusters of up to 50 container instances.
-  If the updater is configured to target a cluster with more than 50 instances, some instances may not be updated.
 
 ### Why do new container instances launch with older Bottlerocket versions?
 

stacks/bottlerocket-ecs-updater.yaml

@@ -10,7 +10,7 @@ Parameters:
   UpdaterImage:
     Description: 'Bottlerocket updater container image'
     Type: String
-    Default: 'public.ecr.aws/bottlerocket/bottlerocket-ecs-updater:v0.1.0'
+    Default: 'public.ecr.aws/bottlerocket/bottlerocket-ecs-updater:v0.2.0'
   LogGroupName:
     Description: 'Log group name for Bottlerocket updater logs'
     Type: String