|
Post by ddeel on Aug 29, 2020 16:32:17 GMT
In the Redfish spec, the "Resource capabilities annotation" section says "Insert capabilities indicate whether a client can perform a POST on the resource."
If insertable=false, is the resulting restriction only for CRUD operations on the resource, or does it also apply to Actions on the resource?
If the restriction also applies to Actions, then it seems like a client would never be able to perform a Reset Action on a Processor resource (for example), where insertable=false. Correct?
|
|
|
Post by mraineri on Sept 1, 2020 13:57:09 GMT
It does not; insertable is purely based on whether or not you can create a new resource within said resource.
When you're performing an action, you're not really performing a POST on the resource itself, but rather the action within the resource. The fact that an action exists implicitly means you can perform a POST on the action.
|
|
|
Post by ddeel on Sept 1, 2020 17:25:55 GMT
Thank you, you've confirmed what I thought should be true. I asked because the spec left me wondering about it. Something like the phrase you used here ("whether or not you can create a new resource within said resource") would be a good clarification for the spec wording.
|
|
|
Post by mraineri on Sept 1, 2020 18:18:26 GMT
Sounds good to me; I'll take that feedback to the forum!
|
|