[API, performance] node-results returning 'node' object per result when filtered by node
Bug #1651274 reported by
Andres Rodriguez
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Invalid
|
High
|
Unassigned |
Bug Description
When trying to obtain the node results of a specific machine, I noticed that every result returns the node object. For example, if you request the node-results for a specific machine:
maas admin node-results read system_id=7p7w7c
Each result it returns, also returns a node object.
Changed in maas: | |
milestone: | 2.2.0 → 2.2.x |
no longer affects: | maas/2.1 |
Changed in maas: | |
milestone: | 2.2.x → 2.3.0 |
Changed in maas: | |
milestone: | 2.3.0 → 2.3.x |
tags: | added: performance |
no longer affects: | maas/trunk |
Changed in maas: | |
milestone: | 2.3.x → next |
summary: |
- [2.1, API] node-results returning 'node' object per result when filtered - by node + [API, performance] node-results returning 'node' object per result when + filtered by node |
Changed in maas: | |
milestone: | next → none |
To post a comment you must log in.
Yeah, that's really weird and inefficient. I hope no one is relying on this behavior, but I think it would probably be safe to cut it down. Rather than doing:
"node": {
# all the things
}
We could do:
"node": {
"system_id": "7p7w7c",
"hostname": "rocking-socks"
}
That way there will still be enough information in the response for someone to figure out which node it came from.