Closed Bug 1211930 Opened 11 years ago Closed 10 years ago

Create unlisted add-on with API

Categories

(addons.mozilla.org Graveyard :: API, defect, P2)

Product:
addons.mozilla.org Graveyard
Component:
API
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: kumar, Assigned: mstriemer)

References

Details

Because unlisted add-ons do not require a lot of fields, we can probably create an API endpoint to upload a brand new unlisted add-on. This would complement bug 1208561 which is an API endpoint for uploading new versions of an existing add-on.
Blocks: 1206158
Assignee: nobody → kumar.mcmillan
We might be able to use the upload new version API to handle this. That endpoint could create an add-on if it doesn't exist.
Upload new version API: bug 1208561.
Priority: -- → P1
Priority: P1 → P2
Iteration: --- → 44.3 - Nov 2
Depends on: 1216780
Iteration: 44.3 - Nov 2 → 45.1 - Nov 16
I think this got fixed naturally in bug 1208561. Anyway, it works as expected now. When you run `jpm sign` on an add-on that doesn't exist yet, it will create it (unlisted).
Assignee: kumar.mcmillan → mstriemer
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.