SameerMesiah97 commented on PR #69886: URL: https://github.com/apache/airflow/pull/69886#issuecomment-4985704771
> What's here looks pretty clean, but it's only adding "thin" Operators. There are no sensors, Triggers, Waiters, etc. Should we expect to have any of those for the ECR usecase? Do we expect it to be very fast in all cases? Even failure paths where waits and retries may happen at the boto level? I was thinking the same thing. I briefly considered the suggestion to add deferrable mode to the create and delete repository operators but I was hesistant because I was not confident that they would be long-running processes. If @AlejandroMorgante can do some basic manual tests to see how long these operations take on average, that would be great. We can decide if waiters, triggers etc are worth it. I do agree the operators are thin, which does call into question their value. But my understanding is that these operators fill a gap in the API at the highest level of abstraction. It would be natural for users to expect them for ECR (as I imagine that this is a fairly popular AWS service). -- 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]
