Closed
Bug 885874
Opened 13 years ago
Closed 13 years ago
Store manifest in db
Categories
(Marketplace Graveyard :: General, enhancement, P5)
Tracking
(Not tracked)
RESOLVED
FIXED
2013-07-04
People
(Reporter: robhudson, Assigned: robhudson)
References
Details
(Whiteboard: [qa-])
In code we're using `get_manifest_json` more and more. Since this hits the file system and for packaged apps reads a zip file, it seems advantageous to store the manifest for easier and faster access.
Note: For hosted apps we need to keep it updated to track changes in the manifest on the servers. Perhaps we store it upon submission, and updated at approval time, then keep it updated when we ping manifests nightly.
|
||
Comment 1•13 years ago
|
||
The manifest is already stored in the validation output, for the record.
|
||
Updated•13 years ago
|
Severity: normal → enhancement
Priority: -- → P5
|
Assignee | |
Comment 2•13 years ago
|
||
Can we bump the priority a little? It would greatly simplify our tests (don't have to mock FS calls all over the place) and also avoid lots of filesystem hits, which may be more important if/when we get on S3.
|
|
Assignee | |
Updated•13 years ago
|
Assignee: nobody → robhudson.mozbugs
|
|
Assignee | |
Comment 3•13 years ago
|
||
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Whiteboard: [qa-]
Target Milestone: --- → 2013-07-04
You need to log in
before you can comment on or make changes to this bug.
Description
•