REST API exposes duplicate methods
Bug #1418443 reported by
aeva black
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Ironic |
Won't Fix
|
Medium
|
Michael Turek | ||
Bug Description
The REST API currently exposes two sets of duplicate methods:
Both of these return a collection of nodes:
GET /v1/chassis/
GET /v1/nodes?
Both of these return a collection of ports:
GET /v1/nodes/
GET /v1/ports?
I do not believe that a REST API should expose multiple paths to provide the exact same resources, as in the first two cases. I suggest we remove support (by first marking it deprecated for 1 - 2 cycles, then removing) for both of these searches
GET /v1/nodes?
GET /v1/ports?
| tags: | added: api |
| Changed in ironic: | |
| status: | New → Triaged |
| importance: | Undecided → Medium |
| Changed in ironic: | |
| milestone: | none → next |
| Changed in ironic: | |
| assignee: | nobody → Michael Turek (mjturek) |
| Changed in ironic: | |
| milestone: | next → none |
Revision history for this message
| Vladyslav Drok (vdrok) wrote | #1 |
| Changed in ironic: | |
| status: | Triaged → Won't Fix |
To post a comment you must log in.
I think following the discussions I remember, we 1. agreed to still have both; 2. can not remove anything anymore. so this can be done only in v2 api. closing this for now.