Could you have some guides that explain the usage of HttpPushUri? I'm in need of help on this to add support for softwareupdate via redfish on one of the embedded product.
The HttpPushUri and the related 'target' properties are really the end of what is specified in Redfish. The actual implementation of a "push model" software update is not specified nor standardized. These properties were added to allow software to discover the existence of this type of support, but as there are many different, vendor-specific implementations, we did not attempt to define a new, standard, mechanism.
I have checked and decided to use like this URI /UpdateService/SoftwareInventory/<ID>/Actions/Oem/Upadte.<ID> to have the software update implemented. With this, I'm assuming I don't need to any or much changes to SoftwareInventory schema, because this schema already has the support for OemActions. Can you please let me know if I'm wrong and help me with the right approach for this.
And also I'm assuming <ID> navigation is supported for Oem actions as well with the default schema. Please comment on this.