Hello, We've had a requirement for Airflow to be able to start DAG Runs and check on the state of tasks in a specific DAG Run via API. We'd seen that an experimental API had been put in place and expanded on this, but there has since been a significant overhaul, mostly around security and the setup in this PR: https://github.com/apache/incubator-airflow/pull/1783
Before we rework our additions (https://github.com/owlabs/incubator-airflow/pull/11, https://github.com/owlabs/incubator-airflow/pull/11, https://github.com/owlabs/incubator-airflow/pull/14) , we thought it might be worth asking if anybody had any thoughts about what we've done so far and whether we're treading on anybody else's toes with these features. The endpoints that we've written are: - Get details of a task instance - Create a DAG Run (this is somewhat covered by the trigger_dag endpoint that has now been added, but we also have a version to allow you to specify the execution date) - Add a value to xcom for a task instance (initially required the task to exist, but we had a use to be able to add xcom for tasks that didn't exist, so we removed that restriction) Is anybody else working on these endpoints or any other significant changes to this area that we'd do better to wait for before we rework these for PR? Thanks, Luke Maycock OLIVER WYMAN [email protected]<mailto:[email protected]> www.oliverwyman.com<http://www.oliverwyman.com/> ________________________________ This e-mail and any attachments may be confidential or legally privileged. If you received this message in error or are not the intended recipient, you should destroy the e-mail message and any attachments or copies, and you are prohibited from retaining, distributing, disclosing or using any information contained herein. Please inform us of the erroneous delivery by return e-mail. Thank you for your cooperation.
