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

Allow devices to access details of the snapshot running on them #94

Closed
robmarcer opened this issue Jun 2, 2023 · 1 comment · Fixed by FlowFuse/flowfuse#2377
Closed
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:XS - 1 Sizing estimation point
Milestone

Comments

@robmarcer
Copy link
Contributor

Description

When working with large sets of devices, it's fair to assume that during a migration to a new snapshot that some devices will continue to run the old snapshot for longer than others.

Where the devices are collecting data from sensors and passing it to a central time series database it would be useful if the data could be tagged as originating from a given snapshot.

That would allow HMIs both on the shop-floor and in offices to understand which data was generated by a specific snapshot and where needed highlight data from an old build.

@robmarcer robmarcer added needs-triage Needs looking at to decide what to do feature-request New feature or request that needs to be turned into Epic/Story details labels Jun 2, 2023
@knolleary knolleary added the size:XS - 1 Sizing estimation point label Jun 30, 2023
@knolleary knolleary added this to the 1.9 milestone Jun 30, 2023
@Steve-Mcl
Copy link
Contributor

Verified staging -> device

Image

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:XS - 1 Sizing estimation point
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants