User:Bhearsum/Balrog/Administration: Difference between revisions

m
 
(5 intermediate revisions by the same user not shown)
Line 31: Line 31:
* Add, modify, or delete a custom rule
* Add, modify, or delete a custom rule
* Add, modify, or delete a release
* Add, modify, or delete a release
* Add, modify, or delete a permission for a known or unknown user
* View history of changes to rules, releases or permissions
* Rollback to previous versions of a rule, release or permission.


=== UI ===
=== UI ===
TBD
==== Permissions ====
===== permissions.html =====
permissions.html is the entry point for managing user permissions. It...
* Contains a list of all known users (which is to say, all unique usernames in the permissions table), with links to user_permissions.html for each of them.
* Has a form that a new username can be entered into, which redirects to user_permissions.html for the new user upon submission.
 
Because AUS doesn't perform authentication, no details besides username are needed when "creating" a new username.
 
===== user_permissions.html =====
user_permissions.html allows for creation, editing, and deletion of permissions for a specific user. It...
* Lists existing permissions, and allows for deletion or editing of their options.
** Only known options for the permission are listed.
* Allows new permissions to be given to the user
** Only known permissions are listed


= Logging & Rollback =
= Logging & Rollback =
Line 68: Line 84:


<p>Build machines will also have an account they must use, and will only be allowed to make changes to a limited set of things:</p>
<p>Build machines will also have an account they must use, and will only be allowed to make changes to a limited set of things:</p>
* /releases/[name]
** For creating new nightly or release builds
* /releases/[name]/builds/[platform]/[locale] PUT
* /releases/[name]/builds/[platform]/[locale] PUT
** For adding new nightly or release builds.
** For adding details of builds and repacks
** This method can implicitly create required intermediaries, should we grant those too, for clarity?
** This method can implicitly create required intermediaries, should we grant those too, for clarity?
* /rules/[id] POST
* /rules/[id] POST
Line 163: Line 181:
| rowspan=3 |/releases/[name]/builds/[platform]/[locale]
| rowspan=3 |/releases/[name]/builds/[platform]/[locale]
| rowspan=3 | PUT
| rowspan=3 | PUT
| rowspan=3 | details - the JSON blob associated with this build
| details - the JSON blob associated with this build
| rowspan=3 | Update the build with the supplied JSON data. If any of the named release, platform, or locale don't exist, they will be created. If the specific build already exists, it will be overwritten with the supplied information.
| rowspan=3 | Update the build with the supplied JSON data. If any of the named release, platform, or locale don't exist, they will be created. If the specific build already exists, it will be overwritten with the supplied information.
| 200 - Build modified
| 200 - Build modified
|
|
|-
|-
| product
| 201 - Build created
| 201 - Build created
|
|
|-
|-
| version
| 400 - The details value is malformed or NULL.
| 400 - The details value is malformed or NULL.
| errmsg
| errmsg
Line 344: Line 364:
|
|
|-
|-
| rowspan=2 | /users/[username]/permissions/[permission]
| rowspan=3 | /users/[username]/permissions/[permission]
| rowspan=2 | PUT
| rowspan=3 | PUT
| rowspan=2 | options - a JSON object whose keys are option names and values are option values
| rowspan=3 | options - a JSON object whose keys are option names and values are option values
| rowspan=2 | Update the permission with the supplied arguments. If it does not exist, it will be created
| rowspan=3 | Update the permission with the supplied arguments. If it does not exist, it will be created
| 200 - Permission modified
| 200 - Permission modified
|
|-
| 201 - Permission created
|
|
|-
|-
canmove, Confirmed users
6,441

edits