guan404ming commented on code in PR #55277: URL: https://github.com/apache/airflow/pull/55277#discussion_r2329636704
########## airflow-core/docs/core-concepts/params.rst: ########## @@ -349,10 +349,61 @@ The following features are supported in the Trigger UI Form: - If you want to have params not being displayed, use the ``const`` attribute. These Params will be submitted but hidden in the Form. The ``const`` value must match the default value to pass `JSON Schema validation <https://json-schema.org/understanding-json-schema/reference/generic.html#constant-values>`_. - On the bottom of the form the generated JSON configuration can be expanded. - If you want to change values manually, the JSON configuration can be adjusted. Changes in the JSON will be reflected in the form fields. + If you want to change values manually, the JSON configuration can be adjusted. Changes are overridden when form fields change. +- 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`` (default is single mode), + and add query parameter to the URL in the form, you can check the parameters and examples below. - Fields can be required or optional. Typed fields are required by default to ensure they pass JSON schema validation. To make typed fields optional, you must allow the "null" type. - Fields without a "section" will be rendered in the default area. Additional sections will be collapsed by default. +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. Review Comment: The fields in the form would dynamically change based on user's config. Thus, we may not only need to handle these specific fields but we should handle all fields passed. The implementation is quite like https://github.com/apache/airflow/pull/54783 -- 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: commits-unsubscr...@airflow.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
