Allow a dev-mode device at Stage 0 to be triggered #5089
Merged
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.
Closes #5079
Description
This updates the UI constraints applied around Pipelines to allow a Device in Dev Mode to be a valid first stage in a pipeline.
This simplifies the workflow for using pipelines with Dev Mode devices; you don't have to take the device out of dev mode in order to move its snapshot to other devices.
This is a simple iteration that allows for the existing Deploy Actions to be chosen. There is scope to add a 'Create Snapshot' action - but that would only work if the device was in dev mode. Given the complications that introduces, in the spirit of fast iteration, I'm going with the existing available actions.
The workflow is then:
This last point is one small potential gotcha. Whilst the device is in dev mode, the 'active' snapshot is whatever snapshot was deployed to the device before it was put into dev mode. The 'latest' snapshot is the most recently created one.
In terms of UX changes, for a Stage0 device in dev mode, I've removed the red warning banner, but left the warning text in place.