Closed
Bug 1026070
Opened 11 years ago
Closed 8 years ago
support blob data migration
Categories
(Release Engineering Graveyard :: Applications: Balrog (backend), defect, P3)
Release Engineering Graveyard
Applications: Balrog (backend)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: bhearsum, Unassigned)
Details
(Whiteboard: [lang=js][lang=python][ready])
Currently, whenever we change the blob format we need to lock rules into an unchanging blob (ie, the dated version of the nightlies), delete the changing version (-latest), and wait for data to repopulate before switching back.
If we had the ability to "upgrade" blobs we could do upgrades like this without any delay to nightly updates.
This might get trickier when we add h264 support, because blobs won't be a linear stream. We'll need to have specific ways to do point to point upgrades (ie, V2 -> V3, h264V1 -> h264V2).
Reporter | ||
Comment 1•11 years ago
|
||
ianconnolly suggested that https://github.com/podio/valideer might be useful here, which would might let us do this and bug 1022649 in one go.
Reporter | ||
Comment 2•8 years ago
|
||
We've had jsonschemas for blobs for awhile now, this might be a little easier. We still need:
- Migration code for AppRelease blobs
- An API endpoint that tries to upgrade a blob
- UI integration
Whiteboard: [lang=js][lang=python][ready]
Reporter | ||
Updated•8 years ago
|
Priority: -- → P3
Comment 3•8 years ago
|
||
Hi,
How can I help with this?
Reporter | ||
Comment 4•8 years ago
|
||
This hasn't been a big issue in reality. Probably not worth fixing - any efforts are better spent on other features.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
Updated•5 years ago
|
Product: Release Engineering → Release Engineering Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•