Warning: This is an experimental API

Overview

This page shows the usage of the Component SLA Types API, please see the following for more details.

Test tools

You can use curl in terminal, with -X method (GET|POST|PUT|DELETE), -d data (a json string). or GUI plugins for browsers, such as RESTClient, RESTConsole.

Documents & examples

Method: GET

URL: /rest_api/v1/component-sla-types/

Query Params:

  • description (string)
  • name (string)
  • ordering (string) Comma separated list of fields for ordering results.
    • To sort by a field in descending order, prefix its name with minus (e.g. -name).
    • Use double underscores for nested field names (e.g. parent__child for {"parent": {"child": ...}}).

Following filters can be used to show only specific fields. This can make response time faster. Format is list or single value (JSON: {"fields": ["a","b"]} or {"fields": "a"}, in URL: ?fields=a&fields=b).

  • fields (list | string) Fields to display (other fields will be hidden).
  • exclude_fields: (list | string) Fields NOT to display (overrules fields).

Response:

{
    "count": int,
    "next": url,
    "previous": url,
    "results": [
        {
            "id": int,
            "name": string,
            "description": string
        }
        ...
    ]
}

Method: GET

URL: /rest_api/v1/component-sla-types/{id}/

Response:

{
    "id": int,
    "name": string,
    "description": string
}

Method: POST

URL: /rest_api/v1/component-sla-types/

Parameters:

  • name: the name of the SLA
  • description: the optional description of the SLA

Data:

{
    "name": string,
    "description": string
}

Response:

{
    "description (optional, default=null)": "string", 
    "id (read-only)": "int", 
    "name": "string"
}

It is possible to create this resource in bulk. To do so, use the same procedure as when creating a single instance, only the request body should contain a list of JSON objects. The response you get back will also contain a list of values which you would obtain by submitting the request data separately.

Method:

PUT/PATCH: for update

Parameters:

  • name: the name of the SLA. This is not a modifiable value.
  • description: the description of the SLA

Data:

{
    "name": string,
    "description": string
}

URL: /rest_api/v1/component-sla-types/{id}/

Response:

{
    "id": int,
    "name": string,
    "description": string
}

Example:

PUT:

curl -X PUT -H "Content-Type: application/json" https://pdc.fedoraproject.org/rest_api/v1/component-sla-types/1/ \
        -d '{"name": "security_fixes", "description": "All upstream security fixes will be applied"}'
# Output
{
    "id": 1,
    "name": "security_fixes",
    "description": "All upstream security fixes will be applied"
}

PATCH:

curl -X PATCH -H "Content-Type: application/json" https://pdc.fedoraproject.org/rest_api/v1/component-sla-types/1/ -d '{"description": "A new description"}'
# Output
{
    "id": 1,
    "name": "security_fixes",
    "description": "A new description"
}

Method: DELETE

URL: /rest_api/v1/component-sla-types/{id}/

Response:

STATUS: 204 NO CONTENT

Example:

curl -X DELETE -H "Content-Type: application/json" https://pdc.fedoraproject.org/rest_api/v1/component-sla-types/1/

It is possible to delete multiple items in one request. Use the DELETE method with the same url as for listing/creating objects. The request body should contain a list with identifiers for objects to be deleted. The identifier is usually the last part of the URL for deleting a single object.

It is possible to update multiple objects in one request. Use the PUT or PATCH method with the same url as for listing/creating objects. The request body should contain an object, where keys are identifiers of objects to be modified and their values use the same format as normal update.

Browsable GET

GET /rest_api/v1/component-sla-types/
HTTP 200 OK
Allow: GET, POST, PUT, PATCH, DELETE, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "count": 4,
    "next": null,
    "previous": null,
    "results": [
        {
            "id": 1,
            "name": "bug_fixes",
            "description": "Bug fixes"
        },
        {
            "id": 3,
            "name": "rawhide",
            "description": "Rolling rawhide.  Generally, tracks upstream."
        },
        {
            "id": 2,
            "name": "security_fixes",
            "description": "Security fixes"
        },
        {
            "id": 4,
            "name": "stable_api",
            "description": "Will do our best not to break API."
        }
    ]
}