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 may be useful if the commands you can run via the debug sockets include triggering operator to execute what it would normally do on a schedule synchronously at any time.
This would be useful for example for conformance tests to avoid having to wait for a scheduled run to have your system reach the desired state.
Sometimes you may also want to execute a schedule immediately to solve some problem where you cannot wait for the scheduled run.
You can already do this now by running the hook and giving it the correct inputs. E.g.:
But this is somewhat clumsy and needs adapting to each hook, a simple command like shell-operator hook $myhook run-schedule $schedulename would be convenient.
The text was updated successfully, but these errors were encountered:
Alternatively a new dumping command similar to hook snapshot which would dump the required binding context json of a hook so one can run the hook manually from it without the need to change it would also be sufficient.
It may be useful if the commands you can run via the debug sockets include triggering operator to execute what it would normally do on a schedule synchronously at any time.
This would be useful for example for conformance tests to avoid having to wait for a scheduled run to have your system reach the desired state.
Sometimes you may also want to execute a schedule immediately to solve some problem where you cannot wait for the scheduled run.
You can already do this now by running the hook and giving it the correct inputs. E.g.:
But this is somewhat clumsy and needs adapting to each hook, a simple command like
shell-operator hook $myhook run-schedule $schedulename
would be convenient.The text was updated successfully, but these errors were encountered: