v3.2.0 - OIDC Support, Docker Label Updates and Container Secrets Update Support

Added Parameters

The deploy-service-update, run-task, update-task-definition-from-json and update-task-definition jobs now support authorization using OpenID Connect. To generate temporary AWS keys, a valid role-arn and context must be provided

• aws-region: AWS region to operate in.
• profile-name: AWS profile name to be configured.
• role-arn: The Amazon Resource Name (ARN) of the role that the caller is assuming. Role ARN must be configured for web identity.
  -role-session-name: An identifier for the assumed role session.
• session-duration: The duration of the session in seconds

The update-service and update-task-definition commands now support updating container secrets and Docker labels in ecs task definitions

• container-secret-updates: Use this to update or set the values of secret variables that will be defined for the containers.
• container-docker-label-updates: Use this to update or set the values of docker label variables that will be defined for the containers.

What's Changed

• feat: implement container secret updates by @brivu in #182
• feat: implement container-docker-label-updates by @brivu in #183
• docs: updated readme and usage examples by @brivu in #185
• feat: oidc implementation by @brivu in #184

Full Changelog: v3.1.0...v3.2.0

v3.1.0 - Implementation of capacity provider strategy and bug fixes

Added Parameters

• deployment-config-name: Enables users to add a predefined deployment configuration when creating a Blue/Green Deployment in CodeDeploy
• codedeploy-capacity-provider-name: The name of AWS Capacity Provider to be added to CodeDeploy deployment. Must be used with capacity-provider-base and capacity-provider-weight.
• codedeploy-capacity-provider-base: The base of AWS Capacity Provider to be added to CodeDeploy deployment. Must be used with codedeploy-capacity-provider-name and codedeploy-capacity-provider-weight.
• codedeploy-capacity-provider-weight: The weight of AWS Capacity Provider to be added to CodeDeploy deployment. Weight must be greater than 0. Must be used with codedeploy-capacity-provider-name and codedeploy-capacity-provider-base.

What's Changed

• feat: implement capacity provider strategy by @brivu in #172
• fix: deploy-ecs-scheduled-task errors by @kxhira in #173
• fix: ephemeral storage retention by @brivu in #177
• fix: terraform force delete by @brivu in #178
• fix: added profile-name parameter by @brivu in #179
• feat: implement deployment-config-name parameter by @brivu in #180

New Contributors

• @kxhira made their first contribution in #173

Full Changelog: v3.0.0...v3.1.0

v3.0.0 - Implementation of deploy-ecs-scheduled-task command and bug fixes

Added Commands

deploy-ecs-scheduled-task - Deploy an ECS Scheduled Task Rule after updating a task definition.

Added Parameters

• rule-name: The name of the scheduled task's rule to update.

What's Changed

• fix!: renamed cluster-name parameter to cluster for consistency by @brivu in #169
• feat: added deploy-ecs-scheduled-task command by @brivu in #168
• fix: added maxsplit=1 to split method to handle base64 values by @brivu in #170
• chore: update fargate spot description by @brivu in #171

Full Changelog: v2.3.0...v3.0.0

v2.3.0 - profile-name implementation, ECS CLI support and many more fixes and features

This minor version change addresses the following:

Added Commands

install-ecs-cli - This command installs the aws ecs cli on Linux and MacOS based images.

Added Parameters

• profile-name: Use a defined aws profile with ever aws ecs command
• run-task-output: Specify a local json file to save the output logs from the aws ecs run-task command.
• enable-circuit-breaker: Determines whether a service deployment will fail if the service can't reach a steady state.
• previous-revision-number: Retrieve a previous task based on definition number
• run-time-platform: Extracts runtimePlatform as a parameter from a previous task definition and enables it's usage when registering a new task definition.

What's Changed

• [semver:major] ECS Orb 2.0 Update by @KyleTryon in #118
• [semver:minor] Always allow platform-version overrides by @lokst in #122
• [semver:minor] Add support for tagging of task-definition to update-service command by @dgeorges in #127
• [semver:patch] fix unexpected string interpolation when using the task-definition-tags argument by @dgeorges in #131
• [semver:skip] Bump py from 1.7.0 to 1.10.0 by @dependabot in #129
• ci: Orb tools 11 migration by @brivu in #150
• chore: update executors to use cimg images by @brivu in #151
• fix: Update Terraform and AWS Provider versions by @brivu in #152
• feat: Add profile-name Parameter by @brivu in #153
• feat: Added runtime-platform parameter by @brivu in #155
• feat: Added previous-revision-number parameter by @brivu in #156
• feat: Added enable-circuit-breaker parameter by @brivu in #157
• feat: Added enable-circuit-breaker parameter for Code Deploy by @brivu in #158
• feat: implement install-ecs-cli command by @brivu in #162
• fix: Blue/Green deployment - moved timeout parameter to proper place by @geoL86 in #163
• fix: addressed override parameter interpolation by @brivu in #165
• feat: implement run-task-output parameter by @brivu in #167

Issues closed

1. Upgrade aws-cli orb to auto install the CLI when setting up the AWS env #164
2. Variable interpolation in overrides JSON #160
3. Support AWS CLI profile name to override credentials #148
4. Changes arch from Linux/X86_64 #147
5. run-task overrides fails to evaluate env arguments #146
6. update-task-definition command remove the runtime-platform information #137
7. Update run-task command to give access to the output from the aws cli #135
8. feat: Implement deployment circuit breaker with rollback for deployment controller of type CODE_DEPLOY #134
9. verification-timeout parameter is ignored in aws-ecs/update-service command #133
10. Enable circuit breakers #125
11. Support Resource Tags #120
12. Need to return the taskarn from run_task command #102
13. Enhance run-task to allow streaming of logs from ecs task and waiting till completion #101
14. No defaults for launch type on consumption of run-task #87
15. Support ecs-cli compose functionality #82
16. Support cross-account deploys #41

New Contributors

• @KyleTryon made their first contribution in #118
• @dgeorges made their first contribution in #127
• @dependabot made their first contribution in #129
• @brivu made their first contribution in #150
• @geoL86 made their first contribution in #163

Full Changelog: minor-release-v1.4.0...v2.3.0

minor-release-v1.4.0: [semver:patch] Add exit code 1 on failed deployment (#113)

Currently, code deploy failures do not fail the job.  This adds a exit code so that the job fails properly and users are notified when a deployment isn't successful

minor-release-v1.3.0: Merge pull request #106 from alekhrycaiko/verify-deployment-completion

Code Deploy (Blue/Green) Verify Deployment Status.

minor-release-v1.2.0: Merge pull request #88 from Xheno/pr-85

Set an optional parameter on whether to run update-task-definition in update-service.

minor-release-v1.1.0: Merge pull request #91 from a10waveracer/address_pr

Add command support for --cli-input-json

patch-release-v1.0.5: Merge pull request #90 from CircleCI-Public/bugfix-asterisk-expansion

Prevent asterisk expansion when asterisk is present in task definition value [semver:patch]

patch-release-v1.0.4: Merge pull request #84 from CircleCI-Public/add-overrides-option

Enhancement: Add overrides parameter to run-task job and command