Node history does not support sorting and specified fields query
Bug #2026289 reported by
Kaifeng Wang
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ironic |
Triaged
|
Wishlist
|
Unassigned | ||
Bug Description
Node history API does not accept sort_key and fields as other endpoints, it would be useful to align with other endpoints to support descending query (newest event first) and return selectable fields by operators.
| tags: | added: rfe |
| Changed in ironic: | |
| importance: | Undecided → Wishlist |
Revision history for this message
| Julia Kreger (juliaashleykreger) wrote | #1 |
| Changed in ironic: | |
| status: | New → Confirmed |
| status: | Confirmed → Triaged |
To post a comment you must log in.
From a usage standpoint, it was always intended to be a "give me an ordered list of events as they occurred" interfacce, so sorting may not really be a thing we want to deal with. Field level queries, there is just not much there and I'm not sure we want to do API level field selection. Patches would be welcome of course.