You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It'd be useful for some ad-hoc/manual workloads to be able to define structure for the JSON used in manual triggered.
This could be either a JSON schema, example/presets trigger payloads, or both.
Use case / motivation
For some use cases we allow triggering jobs with different parameters manually, e.g. disabling some notifications, or triggering more debug logs, or a a different behaviour.
As the manual trigger UI is fairly basic, there's no way of hinting this to users (aside from documentation in the code/UI, however the DAG level documentation is not shown on the manual trigger page so this is of little help at the time of triggering).
The text was updated successfully, but these errors were encountered:
Description
It'd be useful for some ad-hoc/manual workloads to be able to define structure for the JSON used in manual triggered.
This could be either a JSON schema, example/presets trigger payloads, or both.
Use case / motivation
For some use cases we allow triggering jobs with different parameters manually, e.g. disabling some notifications, or triggering more debug logs, or a a different behaviour.
As the manual trigger UI is fairly basic, there's no way of hinting this to users (aside from documentation in the code/UI, however the DAG level documentation is not shown on the manual trigger page so this is of little help at the time of triggering).
The text was updated successfully, but these errors were encountered: