f3ba347b06
In change I13f32e6ca9be9ed4eb42398aace47e3c5205a81f, we introduced support for a 'details' parameter to various proxy methods that supported it. Unfortunately there was a bug in the baremetal proxy layer changes, which were using a mixin to modify the 'Resource.list' class method to allow listing detailed responses easily via the resource layer. This necessitated a revert, change Icc70bbdc06b5f32722a93775aee2da4d7b7ca4ae. Take another go at this by reverting the revert and making the necessary changes to the mixin and proxy layer to make things compatible. We also fix a class of bugs whereby certain resources have the mixin applied, resulting in them attempting to use legacy path-based mechanism to retrieve detailed resources (GET /resource/detail) despite not supporting this. Change-Id: I6acbcb4d9af35e68c04bb86e50c8844487bd7d6c Signed-off-by: Stephen Finucane <stephenfin@redhat.com>
15 lines
330 B
YAML
15 lines
330 B
YAML
---
|
|
features:
|
|
- |
|
|
The following proxy ``find_*`` operations will now retrieve a detailed
|
|
resource by default when retrieving by name:
|
|
|
|
* Bare metal (v1)
|
|
|
|
* ``find_chassis``
|
|
* ``find_node``
|
|
* ``find_port``
|
|
* ``find_port_group``
|
|
* ``find_volume_connector``
|
|
* ``find_volume_target``
|