|
Post by danwarzecha on Sept 11, 2023 18:42:31 GMT
Hello, I'm still new and learning about Redifsh with just a little exposure to it thus far. I'm seeing all kinds of resources and different Schemas that a person can use in order to retrieve data from a backend and then serve it up in the front end, and it got me thinking... Are there specific Redfish Schemas that are used to do the opposite? For example a user would enter something in the front end and use Redfish to share that information with the backend? Maybe that is something that it just was not designed to do?
Thanks,
|
|
|
Post by mraineri on Sept 11, 2023 18:52:40 GMT
The same schemas are used for those cases. Properties marked as read-write are able to be modified by a user through PATCH requests. For example, "LocationIndicatorActive" in "Chassis" is read-write, so a user could perform a PATCH operation with '{ "LocationIndicatorActive": true }' to modify the value to true. Likewise, resource collections marked as insertable are places where a user is allowed to add new members to the resource collection via a POST operation. For example, a user can add a new member to the ManagerAccountCollection resource by performing a POST operation with a request body like '{ "UserName": "NewUser", "Password": "Passwordfornewuser", "RoleId": "Operator" }'.
|
|
|
Post by danwarzecha on Sept 11, 2023 19:40:36 GMT
Thanks!
|
|