REST API exposes duplicate methods

Bug #1418443 reported by aeva black
8
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/XXXX/nodes
  GET /v1/nodes?chassis_uuid=XXXX

Both of these return a collection of ports:
  GET /v1/nodes/XXXX/ports
  GET /v1/ports?node_uuid=XXXX

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?chassis_uuid=XXXX
  GET /v1/ports?node_uuid=XXXX

Tags: api
aeva black (tenbrae)
tags: added: api
Changed in ironic:
status: New → Triaged
importance: Undecided → Medium
aeva black (tenbrae)
Changed in ironic:
milestone: none → next
Michael Turek (mjturek)
Changed in ironic:
assignee: nobody → Michael Turek (mjturek)
Dmitry Tantsur (divius)
Changed in ironic:
milestone: next → none
Revision history for this message
Vladyslav Drok (vdrok) wrote :

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.

Changed in ironic:
status: Triaged → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.