Skip to content

Conversation

@vandonr-amz
Copy link
Contributor

those operations are actually completed instantly.

the doc to deregister says it explicitely:
https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deregister-task-definition.html

When you deregister a task definition revision, it’s immediately marked as INACTIVE.

to register a task, it's less clear, but task definition states show no transition states https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-definition-state.html and expriments show that the task is always returned as active right after having been created.

those operations are actually completed instantly.

the doc to deregister says it explicitely:
https://docs.aws.amazon.com/AmazonECS/latest/developerguide/deregister-task-definition.html
> When you deregister a task definition revision, it’s immediately marked as INACTIVE.

to register a task, it's less clear, but task definition states show no transition states
https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task-definition-state.html
and expriments show that the task is always returned as active right after having been created.
@boring-cyborg boring-cyborg bot added area:providers provider:amazon AWS/Amazon - related issues labels Jun 14, 2023
Copy link
Contributor

@phanikumv phanikumv left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@eladkal eladkal changed the title remove 'wait_for_completion' from ecs register/deregister operators Deprecate wait_for_completion from EcsRegisterTaskDefinitionOperator and EcsDeregisterTaskDefinitionOperator Jun 16, 2023
@eladkal eladkal merged commit 41fb9b4 into apache:main Jun 16, 2023
@vandonr-amz vandonr-amz deleted the vandonr/cleaning branch June 16, 2023 22:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area:providers provider:amazon AWS/Amazon - related issues

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants