anshuksi282-ksolves commented on code in PR #59231: URL: https://github.com/apache/airflow/pull/59231#discussion_r2605406990
########## airflow-core/docs/core-concepts/params.rst: ########## @@ -409,3 +409,52 @@ Disabling Runtime Param Modification The ability to update params while triggering a Dag depends on the flag ``core.dag_run_conf_overrides_params``. Setting this config to ``False`` will effectively turn your default params into constants. + +To pre-populate values in the form when publishing a link to the trigger form you can call the trigger URL ``/dags/<dag_name>/trigger/single`` or ``/dags/<dag_name>/trigger/backfill``, +and add query parameters to the URL. + +There are two trigger form URLs available, each supporting a different set of query parameters: + +* ``/trigger/single``: + - ``conf`` - JSON configuration. + - ``run_id`` - run identifier. + - ``logical_date`` - execution date in ``YYYY-MM-DDTHH:mm:ss.SSS`` format. Defaults to the current timestamp if not provided. + - ``note`` - note attached to the DAG run. + +* ``/trigger/backfill``: + - ``conf`` - JSON configuration, applied to all runs. + - ``from_date`` - start of the backfill window in ``YYYY-MM-DDTHH:mm:ss`` format. + - ``to_date`` - end of the backfill window in ``YYYY-MM-DDTHH:mm:ss`` format. + - ``max_active_runs`` - maximum concurrent runs. Defaults to ``1``. + - ``reprocess_behavior`` - determines how existing runs are reprocessed. Supported values are: + + * ``failed`` - Missing and Errored Runs + * ``completed`` - All Runs + * ``none`` - Missing Runs + + - ``run_backwards`` - if set to true, the backfill is scheduled in reverse order. Defaults to ``false``. + +The trigger form now supports two different ways of providing ``conf`` values. The available input methods are summarized in the table below: Review Comment: > The term "now" is a bit relative... especially if you might read the same text in 10 years if the feature still exists. Good point. I have updated the text to remove the word "now" as suggested. -- 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]
