I asked a very similar question in this thread that might provide a solution in the form of --conf option in trigger_dag.
http://mail-archives.apache.org/mod_mbox/incubator-airflow-dev/201607.mbox/browser However my last comment on the thread suggests exposing similar functionality to the REST api and the UI. On Mon, Jul 11, 2016 at 3:05 PM, Lance Norskog <[email protected]> wrote: > XCOM is a data store for passing data to&between tasks. This is how you > would pass dynamic data to the starting task of a DAG. > Is there a CLI command to add data to XCOM? > > On Mon, Jul 11, 2016 at 2:46 PM, Jon McKenzie <[email protected]> wrote: > > > Unless I'm missing it, it appears like it isn't possible to launch a DAG > > job with initial inputs to the first task instance in the workflow > (without > > specifying those inputs in the DAG definition) > > > > Am I missing something? > > > > So for instance, I want to have user A be able to launch the DAG with > > parameter foo = bar, and user B to be able to launch the same DAG with > foo > > = baz. In my use case, this would be hooked up to a RESTful API, and the > > users wouldn't necessarily know anything about DAGs or what's happening > > behind the scenes > > > > The closest I can think to accomplishing this is to generate run IDs in > my > > REST API, store the (run ID, input) pair in a database, and retrieve the > > inputs in my first task in my DAG. But this seems like a very hamhanded, > > roundabout way of doing it. I'd much rather just create a DagRun with > > task_params that the scheduler automatically associates to the first task > > instance. > > > > Any thoughts? > > > > > > -- > Lance Norskog > [email protected] > Redwood City, CA >
