AlejandroMorgante commented on PR #69886:
URL: https://github.com/apache/airflow/pull/69886#issuecomment-5008059224
The intention is to keep these operators intentionally thin.
`CreateRepository`, `SetRepositoryPolicy`, and `DeleteRepository` are
**synchronous** **request-response** operations with no documented subsequent
lifecycle to monitor.
Their successful responses confirm the completed operation:
`CreateRepository` returns “**the repository that was created**,”
`SetRepositoryPolicy` returns the policy applied to the repository, and
`DeleteRepository` returns “**the repository that was deleted.**” **ECR
provides no applicable waiter for these operations**; its available waiters
only cover image scanning and lifecycle policy previews.
The motivation is to improve Dag expressiveness for common ECR repository
operations while preserving a direct mapping to the underlying APIs. Since
there is no asynchronous state to monitor, adding sensors, triggers, or
deferrable execution would introduce complexity without a corresponding benefit.
You can verify this in the API documentation:
-
https://docs.aws.amazon.com/boto3/latest/reference/services/ecr/client/create_repository.html
-
https://docs.aws.amazon.com/boto3/latest/reference/services/ecr/client/set_repository_policy.html
-
https://docs.aws.amazon.com/boto3/latest/reference/services/ecr/client/delete_repository.html
-
https://docs.aws.amazon.com/boto3/latest/reference/services/ecr.html#waiters
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
