List Inventory Update Events for an Inventory Update
/api/v2/inventory_updates/{id}/events/
Make a GET request to this resource to retrieve a list of inventory update events associated with the selected inventory update.
The resulting data structure contains:
{
"count": 99,
"next": null,
"previous": null,
"results": [
...
]
}
The count field indicates the total number of inventory update events
found for the given query. The next and previous fields provides links to
additional results if there are more than will fit on a single page. The
results list contains zero or more inventory update event records.
Results
Each inventory update event data structure includes the following fields:
id: Database ID for this inventory update event. (integer)type: Data type for this inventory update event. (choice)url: URL for this inventory update event. (string)related: Data structure with URLs of related resources. (object)summary_fields: Data structure with name/description for related resources. The output for some objects may be limited for performance reasons. (object)created: Timestamp when this inventory update event was created. (datetime)modified: Timestamp when this inventory update event was last modified. (datetime)event: (field)counter: (integer)event_display: (string)event_data: (json)failed: (field)changed: (field)uuid: (string)stdout: (string)start_line: (integer)end_line: (integer)verbosity: (integer)inventory_update: (id)
Sorting
To specify that inventory update events are returned in a particular
order, use the order_by query string parameter on the GET request.
?order_by=name
Prefix the field name with a dash - to sort in reverse:
?order_by=-name
Multiple sorting fields may be specified by separating the field names with a
comma ,:
?order_by=name,some_other_field
Pagination
Use the page_size query string parameter to change the number of results
returned for each request. Use the page query string parameter to retrieve
a particular page of results.
?page_size=100&page=2
The previous and next links returned with the results will set these query
string parameters automatically.
Searching
Use the search query string parameter to perform a case-insensitive search
within all designated text fields of a model.
?search=findme
(Added in Ansible Tower 3.1.0) Search across related fields:
?related__search=findme
Request
- application/json
-
page: integer
A page number within the paginated result set.
-
page_size: integer
Number of results to return per page.
-
search: string
A search term.
Response
- application/json
200 Response
object-
changed:
string
Title:
ChangedRead Only:true -
counter:
integer
Title:
CounterRead Only:trueMinimum Value:0 -
created:
string
Title:
CreatedRead Only:true -
end_line:
integer
Title:
End lineRead Only:trueMinimum Value:0 -
event:
string
Title:
EventRead Only:true -
event_data:
object Event data
Title:
Event data -
event_display:
string
Title:
Event displayRead Only:trueMinimum Length:1 -
failed:
string
Title:
FailedRead Only:true -
id:
integer
Title:
IDRead Only:true -
inventory_update:
string
Title:
Inventory updateRead Only:true -
modified:
string
Title:
ModifiedRead Only:true - related: string
-
start_line:
integer
Title:
Start lineRead Only:trueMinimum Value:0 -
stdout:
string
Title:
StdoutRead Only:trueMinimum Length:1 -
summary_fields:
string
Title:
Summary fieldsRead Only:true -
type:
string
Title:
TypeRead Only:true -
url:
string
Title:
UrlRead Only:true -
uuid:
string
Title:
UuidRead Only:trueMinimum Length:1 -
verbosity:
integer
Title:
VerbosityRead Only:trueMinimum Value:0
objectEvent data