Closed kbrock closed 9 months ago
I think this is still a useful method to have as part of the Floe::Workflow
interface even if we don't use it in exe/floe
right now. Plus eventually step_nonblock_wait
could interrupt once the state is ready not just sleep
If we need this method, then don't delete it. I just wanted to highlight that the code was not being called from here or provider-workflow
We are running wait/step_nonblocking_ready? on a list of workflows and no longer on a single workflow
After merging https://github.com/ManageIQ/floe/pull/157, I double checked that all the methods were being called...
Followup / or what this PR should be about:
I do feel that the main loop in
exe/floe
should be moved intoWorkflow.
The version ofwait
isn't quite right and I like the version ofexe/floe
better.