pierrejeambrun opened a new pull request, #70248:
URL: https://github.com/apache/airflow/pull/70248
Re-triggering a Dag with the config of a selected run (the "Trigger DAG w/
config" / "Trigger Again with config" menu item) left the configuration empty —
the JSON editor showed `{}` and the selected run's `conf` was not carried over.
The prefill only pushed the run's `conf` into the param store when the Dag's
declared params were already present. For Dags with no declared params (or
before the params query resolved), that branch was skipped, so the param store
kept its default empty config and the sync effect reset the form back to `{}`,
dropping the run's configuration. The conf is now always propagated to the
param store on prefill; seeding the initial params (for stable section
ordering) still waits until they are available.
Before / after (config carried over from the selected run):
- Before: _screenshot placeholder_
- After: _screenshot placeholder_
---
##### Was generative AI tooling used to co-author this PR?
- [X] Yes — Claude Code (Opus 4.8)
Generated-by: Claude Code (Opus 4.8) following [the
guidelines](https://github.com/apache/airflow/blob/main/contributing-docs/05_pull_requests.rst#gen-ai-assisted-contributions)
--
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]
