User:Bhearsum/Balrog/Administration: Difference between revisions
Jump to navigation
Jump to search
m (moved User:Bhearsum/AUS3/REST to User:Bhearsum/AUS3/Administration) |
No edit summary |
||
Line 1: | Line 1: | ||
This | This page describes and documents the web-based administration interface for AUS3. | ||
== REST API == | |||
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
Line 96: | Line 97: | ||
| Delete the rule | | Delete the rule | ||
|} | |} | ||
== Build machine as a client == |
Revision as of 18:31, 21 July 2011
This page describes and documents the web-based administration interface for AUS3.
REST API
URI | Method | Parameters | Description |
---|---|---|---|
/releases | GET | Retrieves all release names | |
/release/[name] | GET | Retrieve the release identified by "name" | |
/release/[name] | PUT | details - the JSON blob associated with this release | Update the release with the supplied JSON data. If non-existent, it is created. Be careful when using this for existing releases that already have builds added to them -- the JSON blob given here overrides all data for the release, not just platform independent data. |
/release/[name] | DELETE | Delete the release | |
/release/[name]/builds | GET | Retrieve all builds from a release | |
/release/[name]/builds/[platform]/[locale] | GET | Retrieve a specific build from a release | |
/release/[name]/builds/[platform]/[locale] | PUT | details - the JSON blob associated with this build | Update the build with the supplied JSON data. If non-existent, it is created. |
/release/[name]/builds/[platform]/[locale] | DELETE | Delete the build | |
/rule | POST | priority | Create a new rule with the supplied parameters. |
mapping | |||
throttle | |||
update_type | |||
product | |||
version | |||
channel | |||
buildTarget | |||
buildID | |||
locale | |||
osVersion | |||
distribution | |||
distVersion | |||
headerArchitecture | |||
comment | |||
/rule | GET | Same as /rule POST | Retrieve all of the rules that match the specified parameters. Any missing parameters are regarded as wildcards, therefore a request with no parameters returns all rules. |
/rule/[id] | PUT | Same as /rule POST | Update the rule with the supplied parameters. Any missing parameters will be considered NULL. |
/rule/[id] | DELETE | Delete the rule |