Add "test mode" to API signing endpoints
Categories
(addons.mozilla.org :: Security, enhancement)
Tracking
(Not tracked)
People
(Reporter: g.lacava, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:84.0) Gecko/20100101 Firefox/84.0
Steps to reproduce:
I am developing a simple client application to automate signing of some internal browser extensions. As such, I trigger signing of dummy extensions.
Actual results:
The dummy extensions appear under my developer account and have to be manually archived.
Expected results:
The signing service API would benefit from a "test mode" or "demo mode" instance, so that 3rd-party developers don't get their accounts littered with test extensions (i.e. created only to test integration with the API).
Alternatively, an API endpoint to delete one's own extensions (ideally not "archiving") might be ok (if it exists, I couldn't see it in the addons-server docs).
Comment 1•5 years ago
|
||
You can use our staging or development servers for testing and development (I'd recommended staging, as it should be the same config as production, other than having the new deployment of the site 2 days early). https://addons-server.readthedocs.io/en/latest/topics/api/index.html
Description
•