For every search it returns the list of tasks that satisfty the condition. The reason for supporting multiple searches is the UI that might be ending needing periodic updates on task status for various searches at the same time. This way, it is possible to get all the task statuses with one request.
Parametername | Beschreibung |
---|---|
location_id optional |
Scope nach Standorten Validations:
|
organization_id optional |
Scope nach Organisationen Validations:
|
searches optional |
List of uuids to fetch info about Validations:
|
searches[search_id] optional |
Arbitraty value for client to identify the the request parts with results. It's passed in the results to be able to pair the requests and responses properly. Validations:
|
searches[type] optional |
Validations:
|
searches[task_id] optional |
In case :type = 'task', find the task by the uuid Validations:
|
searches[user_id] optional |
In case :type = 'user', find tasks for the user Validations:
|
searches[resource_type] optional |
In case :type = 'resource', what resource type we're searching the tasks for Validations:
|
searches[resource_type] optional |
In case :type = 'resource', what resource id we're searching the tasks for Validations:
|
searches[action_types] optional |
Return just tasks of given action type, e.g. [“Actions::Katello::Repository::Synchronize”] Validations:
|
searches[active_only] optional |
Validations:
|
searches[page] optional |
Validations:
|
searches[per_page] optional |
Validations:
|