-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Snapshot Management for Devices at Application Level #2609
Comments
target audience: @knolleary @MarianRaphael @joepavitt Q1
Would we expect to see the "Snapshots" tab when a device is bound to an instance too? In exploring the design today, it doesnt really fit. For example, following the figma, I currently have this in my design work: Q2
When an instance has no snapshots, the empystate permits snapshot creation. However, currently, a device needs to be in developer mode to create a snaphot and that is done from the developer section on the overview: And lastly, the figma drawings show snapshot creation under a new Developer Mode tab: How should I reconcile this? What is the immediate conclusion/iteration please? |
Will address all of this tomorrow from a UX perspective |
Realise this comment would have been better served here, but just linking for reference. |
There is currently no concept of audit log at application level. Much of the snapshotting and its related audit logs are directed to the project scope auditing. It may well be out of scope for this particular task, but it is something that will be need to be assessed / implemented. Should there be a task or new story around this? Thoughts please? |
Yes please - it is a new task that should be raised and tracked separately. |
It's already been raised: #1978 |
Verified on staging device-snapshots.mp4 |
Description
As soon as Devices can be assigned to applications (without being linked to an Instance). The follow-up question is where to manage and "store" the created Snapshots:
Snapshots at Device Level:
Since Snapshots are currently managed at the Instance Level, the list of snapshots created for each device should be available only for that specific device at Device level. To promote snapshots to other devices, DevOps Pipelines would need to be extended as a subsequent step.
Not in scope:
Snapshots at Application level:
See discussion here: #2335
Tasks
ProjectSnapshots
for snapshot storage, but will require a new column to identifyownerType
. At this iteration, that will benull
, "device" or "instance".projectId
field will be re-used for "device ID". If possible/viable, rename field toownerId
.Have you provided an initial effort estimate for this issue?
I have provided an initial effort estimate
The text was updated successfully, but these errors were encountered: