Closed sytranvn closed 6 months ago
You need to pass --input
to update also. An update replaces the entire schedule configuration, including any input. The various SDKs provide a nicer wrapper around update that lets you change only the fields you want.
You need to pass --input to update also.
Getting existing input of a schedule using cli is also a complex task.
The various SDKs provide a nicer wrapper around update that lets you change only the fields you want.
The solution you give me is ok. And I should not use CLI in this case. But the point is inconsistent behavior between UI/SDK and CLI. Some one might use cli to quickly update cron only then realize they messed up.
What are you really trying to do?
When I update schedule cron value without specifying input, the old workflow input is removed.
Describe the bug
Minimal Reproduction
Triggered workflow has input
{"Input": "As-JSON"}
Terminate the workflow.Schedule is updated to new cron value, but when trigger, new workflow doesn't have input.
Environment/Versions
Additional context