User Story
As a developer working on a remote instance in developer mode, I want to restore a snapshot directly, so that I can revert my work without having to set up a pipeline and exit developer mode.
Description
Currently, when a device is placed into developer mode, it blocks deployment of snapshots to the device. This was done in support of the fleet-mode use case; whilst in developer mode, the flows are being edited locally and should not get overwritten by a pipeline deployment.
This results in an awkward workflow if a device in developer-mode needs to be reverted to an earlier snapshot. It requires setting up a pipeline to set the target snapshot of the device, and then taking the device out of dev mode to allow the snapshot to be deployed.
We have had user feedback from a number of customers who get confused by this.
With auto-snapshot enabled, it is very reasonable for a developer to want to be able to revert their development work back as easily as possible.
For Hosted Instances, the snapshot list includes a 'Restore snapshot' menu option.
We should be consistent and enable this for Remote Instances. This restore snapshot option should trigger a snapshot deploy to the device - regardless of it being in dev mode or not.
We should still block pipeline-triggered deploys for devices in dev mode as that is an expected behaviour.
The device agent will need updating as it is the code that ignores the snapshot updates whilst in dev mode. The update request from the platform will need to contain a new option to indicate if this is a 'manual' update or not so it can distinguish between a pipeline-trigger (to ignore) or a manual restore (which should be actioned).
Decided Solution
Enable snapshot deployment to developer-mode for remote instances. Align the remote instance experience with hosted instances by allowing manual snapshot restores even when a device is in developer mode. Pipeline-triggered deploys continue to be blocked as expected.
This is part of a broader effort to align the Remote Instance and Hosted Instance experiences (see also #6599).
Which customers would this be available to
None
Have you provided an initial effort estimate for this issue?
I have provided an initial effort estimate
User Story
As a developer working on a remote instance in developer mode, I want to restore a snapshot directly, so that I can revert my work without having to set up a pipeline and exit developer mode.
Description
Currently, when a device is placed into developer mode, it blocks deployment of snapshots to the device. This was done in support of the fleet-mode use case; whilst in developer mode, the flows are being edited locally and should not get overwritten by a pipeline deployment.
This results in an awkward workflow if a device in developer-mode needs to be reverted to an earlier snapshot. It requires setting up a pipeline to set the target snapshot of the device, and then taking the device out of dev mode to allow the snapshot to be deployed.
We have had user feedback from a number of customers who get confused by this.
With auto-snapshot enabled, it is very reasonable for a developer to want to be able to revert their development work back as easily as possible.
For Hosted Instances, the snapshot list includes a 'Restore snapshot' menu option.
We should be consistent and enable this for Remote Instances. This restore snapshot option should trigger a snapshot deploy to the device - regardless of it being in dev mode or not.
We should still block pipeline-triggered deploys for devices in dev mode as that is an expected behaviour.
The device agent will need updating as it is the code that ignores the snapshot updates whilst in dev mode. The update request from the platform will need to contain a new option to indicate if this is a 'manual' update or not so it can distinguish between a pipeline-trigger (to ignore) or a manual restore (which should be actioned).
Decided Solution
Enable snapshot deployment to developer-mode for remote instances. Align the remote instance experience with hosted instances by allowing manual snapshot restores even when a device is in developer mode. Pipeline-triggered deploys continue to be blocked as expected.
This is part of a broader effort to align the Remote Instance and Hosted Instance experiences (see also #6599).
Which customers would this be available to
None
Have you provided an initial effort estimate for this issue?
I have provided an initial effort estimate