kaxil commented on issue #47499: URL: https://github.com/apache/airflow/issues/47499#issuecomment-2717699455
I am thinking we should move TriggerDagRunOperator to a separate new “Airflow API provider” from the Standard provider since tasks don’t have access to DB directly. This provider can be built on top of the HTTP provider and the Airflow API. And overtime we can add more hooks and Operators to that provider. This way a dag author can create a separate Airflow Connection for it as the task will need Auth — and it can then work with same or remote Airflow instance. Thoughts anyone? -- 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]
