Closed
Bug 1122263
Opened 11 years ago
Closed 11 years ago
Create langpacks API
Categories
(Marketplace Graveyard :: API, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
2015-02-03
People
(Reporter: andy+bugzilla, Assigned: mat)
References
Details
(Whiteboard: [qa-])
API to create a langpack as per bug 1122255. Should be protected by the permission in bug 1122262.
Comment 1•11 years ago
|
||
As the langpacks will be auto-approved, bug 1105507 is a blocker (I guess).
Depends on: 1105507
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → mpillard
Priority: P3 → P2
Assignee | ||
Comment 2•11 years ago
|
||
Consolidating every langpacks API bug into this one. Also removing dependency on bug 1105507 as it's not mandatory.
No longer depends on: 1105507
Summary: Create an API to create langpacks → Create langpacks API
Assignee | ||
Comment 7•11 years ago
|
||
The API needs to handle:
- GET /langpacks/ - listing available langpacks (with optional filters through query parameters)
- GET /langpacks/<uuid>/ - list a single langpack (probably unused)
- POST /langpacks/ - upload a new langpack .zip file
- PUT /langpacks/<uuid>/ - upload a langpack .zip file to replace a specific langpack
- PATCH /langpacks/<uuid>/ - change the status of a specific langpack (all other fields are manifest-driven so you can't change them without uploading a new package)
- DELETE /langpacks/<uuid>/ - delete a langpack
The unsafe verbs need to be protected by a LangPacks:Something permission. The upload stuff will re-use the submission API to create a fileupload instance and the user will then pass the fileupload instance uuid (if valid) to create or modify a langpack from a .zip package.
Assignee | ||
Updated•11 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 8•11 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → 2015-02-03
Assignee | ||
Updated•11 years ago
|
Whiteboard: [qa-]
You need to log in
before you can comment on or make changes to this bug.
Description
•