|
Post by mharishm on Feb 15, 2024 7:12:56 GMT
As per the schema, ServiceAddresses is of type Array. But in our case in our BMC we support setting only one service address. So even if user sends request to save LDAP configuration with multiple service address like
Our redfish service will only set the first index(192.168.0.110) of the array and will set only that ignoring the other array elements. This information we have noted in our API document as
Is it ok with this approach or does the PATCH call should return 400 bad request even if all other LDAP configurations are valid and can set in BMC?
|
|
|
Post by mraineri on Feb 15, 2024 17:50:14 GMT
This can be covered by the existing "partial success of a PATCH operation" statements in the "PATCH (update)" clause. Your service successfully applied the first array index in the request, thus returning 200 OK is correct. However, you do need to include a message in the response indicating what was ignored/dropped. The "ArraySizeTooLong" message should work for this case to show the client that the remaining elements were dropped.
|
|