Add-ons/Projects/InternalSearch: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
| Line 13: | Line 13: | ||
* authentication of the user | * authentication of the user | ||
Since this gives us a front end that serves out a nice web page and talks to AMO with an API, we've got a basis for our front end rewrite of AMO. This basically is spelled out in | Since this gives us a front end that serves out a nice web page and talks to AMO with an API, we've got a basis for our front end rewrite of AMO. This basically is spelled out in [https://github.com/mozilla/olympia/issues/978 issue 978]. | ||
=== Stretch goal === | === Stretch goal === | ||
* | * [https://github.com/mozilla/olympia/issues/979 User admin search] | ||
Latest revision as of 19:41, 12 January 2016
This is planning or roadmap for the internal search API.
Goals
Allow someone with the appropriate authorisation (likely a reviewer or someone internal to MoCo) to easily search for an add-on and find out:
- given an add-on GUID, slug or primary key tell me
- everything about the add-on including but not limited too:
- if the add on is listed or not
- review queue status
- versions and version status
- files and file status and if the files are signed and how its signed (full or preliminary)
- everything about the add-on including but not limited too:
- a simple search to find add-ons
- authentication of the user
Since this gives us a front end that serves out a nice web page and talks to AMO with an API, we've got a basis for our front end rewrite of AMO. This basically is spelled out in issue 978.