Enable ECS ContainerDependency - DependsOn parameter

[AlexJov]

SUMMARY

Enabling init containers when describing Containers with ECS TaskDefinitions by adding depends_on task configuration option.

ISSUE TYPE

• Feature Idea

COMPONENT NAME

ecs_taskdefinition

ANSIBLE VERSION

> ansible --version
ansible 2.10.4
python version = 3.9.1

ADDITIONAL INFORMATION

Having container dependencies is supported by boto3 lib:
https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/ecs.html#ECS.Client.register_task_definition

However, at the moment is not part of the available parameters to pass with AWS community Ansible collection:

community.aws/plugins/modules/ecs_taskdefinition.py

Line 275 in 130cf3c

response = self.ecs.register_task_definition(**params)

What this feature would enable is having an init container to deliver binaries, for example monitoring (APM) agent files, before starting the essential container with the application.
Without the dependsOn option available, in case of this example, the application starts before files are mounted from the agent's container and fail to attach an agent, or in some cases fails completely.

[ansibullbot]

Files identified in the description:

• [plugins/modules/ecs_taskdefinition.py](https://github.com/['ansible-collections/amazon.aws', 'ansible-collections/community.aws', 'ansible-collections/community.vmware']/blob/main/plugins/modules/ecs_taskdefinition.py)

If these files are inaccurate, please update the component name section of the description or use the !component bot command.

click here for bot help

[ansibullbot]

cc @Java1Guy @jillr @s-hertel @tremble @wimnat
click here for bot help

[alinabuzachis]

Hi @AlexJov, thank you for raising this issue. It seems this parameter is already supported but it was not properly documented in the Ansible module. dependsOn parameter requires platform version >= 1.3.0 for tasks that use the Fargate launch type. Let me know please if it works for you. Thank you.