Get inventory FRU from inventory system path

[Andrei Kartashev]

Hi John,

What are you trying to achieve?
The REST API do just a translation to dbus, so you expect to get
exactly what EntityManager (or other inventory-related daemon) expose.
And EM expose nothing to /xyz/openbmc_project/inventory/system

On Thu, 2020-10-08 at 08:53 +0000, john.chung at mic.com.tw wrote:
> Hi,
>  
> I am trying to get the data from this path “
> https://<bmcip>/xyz/openbmc_project/inventory/system”.
> But only get the following data from this path.
>  
> "/xyz/openbmc_project/inventory/system": {
> "AssetTag": ""
> },
>  
> Here is an example for this path which I expected to get.
>  
>     "/xyz/openbmc_project/inventory/system": {
>         "BuildDate": "",
>         "Cached": 0,
>         "FieldReplaceable": 0,
>         "Manufacturer": "",
>         "Model": "2",
>         "PartNumber": "0000000000000000",
>         "Present": 1,
>         "PrettyName": "",
>         "SerialNumber": "0000000000000000"
>     },
>  
>  
>  
> Only using entity-manager in my project for inventory FRU.
> I could get the FRU data from this path “
> https://<bmcip>/xyz/openbmc_project/inventory/system/board/<name>”
> But the inventory system path is null.
>  
> Any setting I should set for getting FRU from this path?
>  
> Regards,
> John Chung
>  
> This email message and all attachments transmitted with it are
> intended solely for the use of the intended recipient(s) and may
> contain legally privileged and confidential information. If you are
> not the intended recipient of this email, you are hereby notified
> that any disclosure, dissemination, distribution, copying, or other
> use of this message, its attachments or any information contained
> therein is strictly prohibited. If you have received this email in
> error, please contact the sender immediately and please delete it and
> any attachments from your system. Computer viruses can be transmitted
> via email. The sender accepts no liability for any damage caused by
> any virus transmitted by this email. Thank you.
-- 
Best regards,
Andrei Kartashev