harrisjoseph opened a new issue #11054: URL: https://github.com/apache/airflow/issues/11054
**Description** Replace the Configuration JSON text-area with a form that has individual input fields for each key & value. This will remove the need for the user to provide a json object. See hashicorp vault's key-value secrets UI for an example of what this might look like:  - If present these keys and values should be serialised as json client-side and posted to the trigger-dag API endpoint as the `conf` request-parameter. - By default no conf request-parameter is sent. Perhaps a checkbox should be used to determine whether conf is sent at all? - The user may want to add new keys, or remove keys & values that they have previously added. - [PR-10839](https://github.com/apache/airflow/pull/10839) is pre-populating the form with the DAG's default params. The form should be pre-populated with the keys & values from `DAG.params` **Use case / motivation** Currently when triggering a manual DAG run with user-provided runtime parameters, the user has to provide a correctly formatted JSON object. Filling in a form with keys & values will be a significantly better user experience, and will be less error prone & laborious than handling json in a free-text field. This builds on the great work already done on enhancing the Trigger-DAG functionality **Related Issues** Originating PR: https://github.com/apache/airflow/pull/10839 ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
