Skip to content

ecs_taskdefinition idempotency fails for containerDefinition secrets #45

Open
@Alex-Richman

Description

@Alex-Richman

SUMMARY

ecs_taskdefinition idempotency checks fail if secrets are supplied in a containerDefinition.

This appears to be because boto3 doesn't actually return the secrets in describe_task_definition, so the _right_has_values_of_left fails.

Can't really be fixed in Ansible until boto3 is updated (I've raised it with AWS), but useful to have this bug here with the details.

ISSUE TYPE
  • Bug Report
COMPONENT NAME

ecs_taskdefinition

STEPS TO REPRODUCE
ecs_taskdefinition:
  state: present
  force_create: no
  ...
  containers:
    ...
    - name: ...
      secrets: ...
EXPECTED RESULTS

An ecs_taskdefinition call with the same parameters should correctly validate that a task definition revision already exists with the same configuration.

ACTUAL RESULTS

An ecs_taskdefinition with the same parameters (but including secrets config in a containerDefinition) always returns CHANGED, with a new task definition revision created.

https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/ecs.html#ECS.Client.describe_task_definition

Metadata

Metadata

Assignees

No one assigned

    Labels

    affects_2.10bugThis issue/PR relates to a bugmodulemoduleneeds_infoThis issue requires further information. Please answer any outstanding questionsneeds_templateThis issue/PR has an incomplete description. Please fill in the proposed template correctlyneeds_verifiedpluginsplugin (any type)

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions