Skip to content

Releases: awslabs/fargatecli

v0.3.2

05 Sep 10:24
Compare
Choose a tag to compare

0.3.2 (2019-09-05)

Enhancements

  • Relocated from @jpignata's personal GitHub to github.com/awslabs. Thanks for all of your hard work on this tool John :)
  • Removed strict region checking. This means that we don't need to modify the Fargate CLI when new AWS regions come online.

v0.3.1

09 May 05:17
Compare
Choose a tag to compare

0.3.1 (2019-05-09)

Enhancements

  • Added support for ap-south-1, ca-central-1 and ap-northeast-2 regions

The full list of supported regions is now:

  • ap-northeast-1
  • ap-northeast-2
  • ap-south-1
  • ap-southeast-1
  • ap-southeast-2
  • ca-central-1
  • eu-central-1
  • eu-west-1
  • eu-west-2
  • us-east-1
  • us-east-2
  • us-west-1
  • us-west-2

v0.3.0

14 Mar 05:02
Compare
Choose a tag to compare

Enhancements

  • Console output reworked for consistency and brevity
  • macOS users get emoji as a type prefix in console output 🎉 -- disable
    with --no-emoji if you're not into fun
  • Requests and responses from AWS are displayed in full when --verbose is
    passed
  • Added additional AWS Fargate regions
  • Added --task-command flag to allow overriding of the Docker command used by the container
  • If you have a region set in your AWS credentials, use that by default and only fall back to us-east-1 if no region is set
  • Added --assign-public-ip boolean flag, which allows you to control whether a task has a public IP address (default: true)

Bug Fixes

  • Environment variable service commands now return a polite error message when
    invoked without the service name. ([#22][issue-22])
  • Certificate import command re-implemented to work correctly. Previously calls
    to this command always returned "private key not supported" as we were
    incorrectly encoding it to base64 before passing it to the AWS SDK.

Chores

  • Add contributor guide, updated license to repo

v0.2.3

20 Jan 04:51
Compare
Choose a tag to compare

0.2.3 (2018-01-19)

Features

  • Support --task-role flag in service create and task run to allow passing a role name for the tasks to assume. (#8)

Enhancements

  • Use the ForceNewDeployment feature of UpdateService in service restart instead of incrementing the task definition. (#14)

Bug Fixes

  • Fixed issue where we'd stomp on an existing task role on service updates like deployments or environment variable changes. (#8)

v0.2.2

12 Jan 01:01
Compare
Choose a tag to compare

0.2.2 (2018-01-11)

Bug Fixes

  • Fix service update operation to properly validate and run. (#11)
  • Bail out early in service info if the requested service is not active meaning it has been previously destroyed.

v0.2.1

03 Jan 02:36
Compare
Choose a tag to compare

0.2.1 (2018-01-02)

Bug Fixes

  • service create will not run if a load balancer is configured without a port.
  • service create and task run will no longer create a repository if an image is explictly passed.
  • service destroy will remove all references the service's target group and delete it.
  • Fix git repo detection to properly use a git sha image tag rather than a time stamp tag. (#6)
  • Fail fast if a user attempts to destroy a service scaled above 0.

v0.2.0

31 Dec 15:43
Compare
Choose a tag to compare

0.2.0 (2017-12-31)

Features

  • Added --cluster global flag to allow running commands against other clusters rather than the default. If omitted, the default fargate cluster is used. (#2)
  • lb create, service create, and task run now accept an optional --subnet-id flag to place resources in different VPCs and subnets rather than the defaults. If omitted, resources will be placed within the default subnets within the default VPC. (#2)
  • lb create, service create, and task run now accept an optional --security-group-id flag to allow applying more restrictive security groups to load balancers, services, and tasks. This flag can be passed multiple times to apply multiple security groups. If omitted, a permissive security group will be applied.

Bug Fixes

  • Resolved crashes with certificates missing resource records. Certificates that fail to be issued immediately after request would cause crashes in lb info and lb list as the resource record was never generated.

v0.1.2

29 Dec 19:19
Compare
Choose a tag to compare
Bump to 0.1.2

v0.1.1

29 Dec 04:41
Compare
Choose a tag to compare
Bump to 0.1.1

v0.1.0

28 Dec 03:09
Compare
Choose a tag to compare
Add build helpers to Makefile