Confirmed users
528
edits
WebExtensions/Applications: Difference between revisions
→API: Add proposed AMO Signing API changes.
No edit summary |
(→API: Add proposed AMO Signing API changes.) |
||
| Line 69: | Line 69: | ||
== API == | == API == | ||
The [http://addons-server.readthedocs.org/en/latest/topics/api/signing.html signing APIs] for addons.mozilla.org are keyed off the add-on id. Developers using the API would need to know the add-on id, or specify it in mozilla.json. | The [http://addons-server.readthedocs.org/en/latest/topics/api/signing.html signing APIs] for addons.mozilla.org are currently keyed off the add-on id. Developers using the API would need to know the add-on id, or specify it in mozilla.json. | ||
To fix this, we also propose changing the AMO signing API from | |||
'''PUT /api/v3/addons/[string:addon-id]/versions/[string:version]/''' | |||
to | |||
'''PUT /api/v3/addons/''' | |||
and having the server pull the addon-id and version out of the submitted XPI (or generate them if they're missing). | |||
(We should also return that data as fields in the response, so that the calling script would know what they were going to be.) | |||
Tools like web-ext could go through the same steps as AMO. | Tools like web-ext could go through the same steps as AMO. | ||