924922 - Add an HTTP API to register / read / delete non-AMO addons.

Status: RESOLVED WONTFIX

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

Description

[Alexis Metaireau (:alexis)]

The addons-registration project needs to have a way to register new addons and hashs.

Here is the set of proposed APIs:

PUT, DELETE, GET on /api/filereg/addon/{addonid}
PUT, DELETE on /api/filereg/addon/{addonid}/hash/{sha256}

This will use DRF internally because it seems to be the way to go at the moment.
The GET is here only to be consumed by the frontend, and not by the firefox clients which will need to make a huge amount of calls (this will be handled in a different way).

Comment 1

[Alexis Metaireau (:alexis)]

The goal is to ask addon authors to register their addons so we can only
activate known and registered addons on firefox.

I've modified the APIs from comment #0, here are the new ones:

- /addonreg/addons/{addonid}
- /addonreg/hashes/{hash}

This PR also comes with a rip-off of the shared-auth authentication from mkt, the goal being to start implementing a fireplace-like webapp for addons.m.o (see bug 927786)

Comment 2

[Alexis Metaireau (:alexis)]

See https://github.com/mozilla/zamboni/pull/1260. :chuck, r?

Comment 3

[Andy McKay]

I don't think this is a thing anymore.