Description
Describe the issue
Since the playground functionality, we have the possibility in the backend to suspend an execution at a breakpoint, and resume it later.
We made this so it is not tied to the playground functionality at all so we can later bring this functionality on itself inside the UI.
The following changes describes UI only changes to support that.
Start and execution with a breakpoint
When starting an execution, inside the Additional properties options, we can add a breakpoint (or a list of breakpoints) so that, when the execution arrives at this task, it will suspend.
Then, when an execution is suspended at a breakpoint, allow resuming it, optionally setting new breakpoints.
This would be a kind of light debugger for executions.
Add breakpoints to a running execution
Optionaly, we can also allow adding breakpoints to a running execution, this can be useful for operational teams that would stop an execution but not kill it: add a breakpoint to the next task.
This would be racy as the execution could start the task and the breakpoint ignored so we should add a warning about it.
Environment
- Kestra Version: develop