dylanbstorey opened a new issue, #27162: URL: https://github.com/apache/airflow/issues/27162
### Description A "manual intervention" operator as a core component of airflow. ### Use case/motivation Sometimes it is useful/necessary to keep a "human in the loop" for some data processing tasks. In a few occurrences I've had the need allow for an external (non "data") party to be able to release the last stage of a data pipeline as a task - doing this in airflow required us creating an external service + sensor for managing the checkpoint. The general flow looked like this : - task registers lock with external service + sends message to user that it is ready - sensor begins polling for lock release - user clicks link to "clear" the lock - sensor releases downstream tasks. I could see this being useful to other users of airflow, but as a core feature. With the introduction of dataset awareness + deferrable operators, i believe it will also be able to be designed in a better way than back in Airflow 1. ### Related issues Not to my knowledge. ### Are you willing to submit a PR? - [X] Yes I am willing to submit a PR! ### Code of Conduct - [X] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- 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]
