Plugins » Foreman Remote Execution

Part of #12814 was introducing a job invocation state. Currently we use state from foreman tasks which in job context is not ideal for searching (states like planning, planned, scheduled). We should define relevant states for job and use them in all helpers and views instead. We don't want to save state in DB though but rather create a mapping to foreman tasks state and result. We want to avoid another cached state (dynflow task state, foreman task state, execution state).

• queued - not started yet (executor did not create task / scheduled to future)
• running - task exists and should be processed already
• failed - final state with error
• succeeded - final state with success (or even warning)