Do not use runtimePlatform for non-fargate ECS Task Definitions

[okirmis]

SUMMARY

For ECS task definitions, runtime_platform options should be empty for task definitions with non-fargate launch_type (e.g. EC2), because otherwise services will not be able to deploy them. There is no way to avoid this option (runtimePlatform) to be set to a value due to the validations and therefore there is no way to use this module to create non-FARGATE task definitions any more.

ISSUE TYPE

• Bugfix Pull Request

COMPONENT NAME

ecs_taskdefinition

ADDITIONAL INFORMATION

1. Create an ECS task definition with launch type EC2. Omit the runtimePlatform option. This will create an ECS Task definition that specifies LINUX/X86_64 as runtime (should be empty, though, because runtimePlatform only affects FARGATE-launched tasks).
2. Create an ECS service which uses this task definition.
3. The deployment will fail

This situation is resolved when runtimePlatform options are not set. This, however, is not possible at the moment. It also breaks backwards compatibility for non-FARGATE task definitions.

[softwarefactory-project-zuul]

Build succeeded.
https://ansible.softwarefactory-project.io/zuul/buildset/928453e5137641cc8a15fc3f6cc18892

✔️ ansible-galaxy-importer SUCCESS in 4m 32s (non-voting)
✔️ build-ansible-collection SUCCESS in 14m 28s
✔️ ansible-test-splitter SUCCESS in 5m 28s
✔️ integration-community.aws-1 SUCCESS in 18m 38s
Skipped 21 jobs