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
When creating CronWorkflow and running it manually, parameters/arguments cannot be passed as we can in WorkflowTemplate
while I understand this can be an opinionated decision, I think that as long as submitting is possible, we should be able to modify parameters as well
Our use case is BI/Data teams that want to create a scheduled job for ETLs or other jobs, but want to maintain the ability to run them manually with parameters (without creating both CronWorkflow and WorkflowTemplate)
our best option with this is to write a Cron that will re-use the WorkflowTemplate, but that's still 2 places in the UI and 2 files/resources for each job
Example from Airflow of running a scheduled job with config/params
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
When creating CronWorkflow and running it manually, parameters/arguments cannot be passed as we can in WorkflowTemplate
while I understand this can be an opinionated decision, I think that as long as submitting is possible, we should be able to modify parameters as well
Our use case is BI/Data teams that want to create a scheduled job for ETLs or other jobs, but want to maintain the ability to run them manually with parameters (without creating both CronWorkflow and WorkflowTemplate)
our best option with this is to write a Cron that will re-use the WorkflowTemplate, but that's still 2 places in the UI and 2 files/resources for each job
Example from Airflow of running a scheduled job with config/params
Beta Was this translation helpful? Give feedback.
All reactions