Skip to content

AWS ECS - pass all arguments for "register-task-definition" command

Problem to solve

As raised in this issue, the aws ecs register-task-definition command used in this script to create a new version of an AWS task definition for ECS does not pass all existing arguments.

The goal of the script linked just above is to update the location of the new Docker application image. In doing so, it is important to do a strict copy of all other task definition attributes from the current version to the new version.

As a result, by not passing arguments like execution-role-arn, and if this attribute had a value in the current task definition, then it will set to null in the new task definition.

By passing all documented relevant arguments to register-task-definition, we'll make sure not to break anything when registering the new task definition.

cc @csouthard

Intended users

User experience goal

User should be able to deploy to AWS ECS without having task definition discrepancies between two versions.

Proposal

Pass all arguments as outlined in this documentation.

Permissions and Security

Documentation

Availability & Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Is this a cross-stage feature?

Links / references

Edited by Etienne Baqué