[RFE] using ETAG headers would improve API usability
Bug #1605728 reported by
aeva black
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ironic |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
Ironic's REST API does not currently return an ETAG (*) ID in the headers of any responses. Doing so would improve the usability of the API by allowing clients to quickly and easily determine if a resource changed since the last time that client interacted with it (eg, because another client modified it). Sending ETAGs in request headers would also allow the Ironic service to prevent the "lost update problem" (*) and begin using POST in places where we currently only support PATCH requests.
The OpenStack API WG recommends that this header be included by all services.
(*) https:/
Changed in ironic: | |
status: | New → Confirmed |
importance: | Undecided → Wishlist |
Changed in ironic: | |
assignee: | nobody → Galyna Zholtkevych (gzholtkevych) |
Changed in ironic: | |
assignee: | Galyna Zholtkevych (gzholtkevych) → nobody |
status: | In Progress → Triaged |
tags: |
added: rfe-approved removed: needs-spec rfe |
To post a comment you must log in.
I'll be all for just approving this RFE, but let's state how the ETAG will be calculated. Also I'm not sure about "using POST instead of PATCH" bit. The cross-project spec talks about PUT. And anyway I can imagine ETAGs useful with PATCH as well (anything updating capabilities would really appreciated it, e.g. ironic-inspector).