Closed Bug 1138619 Opened 10 years ago Closed 10 years ago

Need an api to upload new versions of add-ons

Categories

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

Product:
addons.mozilla.org Graveyard
Component:
API
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: evold, Unassigned)

References

Details

I'd like to Implement `jpm upload` to have our jpm cli tool https://www.npmjs.com/package/jpm upload the add-ons that it generates to AMO. I was investigating this and it appears there is an oauth method api to do this, based on what I see in https://github.com/andymckay/amo-oauth/blob/master/src/amo.py but I don't think I will be able to use oautho for JPM which is a CLI, since we would have to make the consumer key public.. So we need a new, non-oauth, api to handle upload requests.
Blocks: jpm
I don't think there's a valid objection to OAuth. With the current two-legged scheme, we can always issue consumer keys to users directly. If we add three-legged support, making app-specific consumer keys public will not be a major problem.
We've got jpm sign now and apis behind it allow to add in a new version. Any more APIs will be added in the API project.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
Product: addons.mozilla.org → addons.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.