Skip to content
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

Cross-Instance Snapshot Management #2335

Closed
Tracked by #2334
MarianRaphael opened this issue Jun 26, 2023 · 4 comments
Closed
Tracked by #2334

Cross-Instance Snapshot Management #2335

MarianRaphael opened this issue Jun 26, 2023 · 4 comments
Labels
feature-request New feature or request that needs to be turned into Epic/Story details needs-triage Needs looking at to decide what to do size:XL - 8 Sizing estimation point

Comments

@MarianRaphael
Copy link
Contributor

MarianRaphael commented Jun 26, 2023

Description

Introduce a mechanism to manage and control snapshots at an application level. This feature not only allows the visibility of each snapshot across all application instances, but also permits the assignment of each snapshot to any instance or device within an application.

Have you provided an initial effort estimate for this issue?

I have provided an initial effort estimate

@MarianRaphael MarianRaphael added feature-request New feature or request that needs to be turned into Epic/Story details needs-triage Needs looking at to decide what to do size:XL - 8 Sizing estimation point labels Jun 26, 2023
@MarianRaphael MarianRaphael changed the title Cross-Application Snapshot Management Cross-Instance Snapshot Management Jun 26, 2023
@joepavitt
Copy link
Contributor

permits the assignment of each snapshot to any instance or device

Can I just sanity check what you're meaning here. To move a snapshot from one Instance to another, we'd be using Pipelines. We'd discussed the point that Pipelines should auto-capture a snapshot when a promotion of a stage occurs (to backup existing target stage work before the push, and to capture a snapshot of the flows pushed). Not sure a single "Snapshots" view at the Application level helps here though. Feels like it it could get quite messy?

@MarianRaphael
Copy link
Contributor Author

Indeed, I see where you're coming from. Let me clarify what I had in mind. My initial thought was based on the fact that presently, the only mechanism for updating Devices is through the use of snapshots. In this context, when Devices are managed separately from an Instance at an Application level, snapshots must be accessible from that level.

However, we're now moving toward a model where Devices can be assigned to Pipelines, and Pipelines will essentially serve as the medium for updates. As a result, the "Cross-Instance Snapshot Management" becomes optional.

@MarianRaphael MarianRaphael closed this as not planned Won't fix, can't repro, duplicate, stale Jul 7, 2023
@joepavitt
Copy link
Contributor

yep - I think the point that needs to be captured (if not already) is that we can have multiple entities (most likely devices) bound to a single stage of a pipeline - then that would in theory, mimic the Snapshot workflow.

@knolleary
Copy link
Member

Another point to clarify, the 'Device in pipeline' work about to be completed makes use of the devices being assigned to an instance. The new work allows you to set the target snapshot on the instance when it is deployed to. This will in turn update the assigned devices.

We have not enabled devices to be a direct target in the pipeline stage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature-request New feature or request that needs to be turned into Epic/Story details needs-triage Needs looking at to decide what to do size:XL - 8 Sizing estimation point
Projects
Archived in project
Development

No branches or pull requests

3 participants