fix(checks): require active workflow to proceed with osie/hook #220
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Require active workflow to proceed with serving osie/hook.
Why is this needed
Seems this was intended when #35 led to a merge. It has since fallen out of the codebase 🤷?
Also from this walkthrough
How Has This Been Tested?
I tested this manually. When no workflow was associated:
And when I associated a workflow to the same hardware:
How are existing users impacted? What migration steps/scripts do we need?
Anyone expecting the existing behaviour would be impacted, and would need to create workflows before boot in order to enjoy an osie / hook boot.
Checklist:
I have: