dmtf / redfish-uri-validator Goto Github PK

I had a redfish implementation that incorrectly used /redfish/v1/Schemas instead of /redfish/v1/JsonSchemas. This was caught by Redfish-Service-Validator, but not Redfish-URI-Validator. This tool didn't mention that resource/URI at all in the RedfishURITestReport html document it created.

Hi,

I raised an issue yesterday. When I would like to check it today, I find it is moved to another repository. Please let me know how to track it. Thanks.

Hi,

When I run the tool under Windows with python 3.7, I see below problem and tool hangs at "Logging" step. Also I see YAMLLoadWarning message.

Command:
D:\scripts\Redfish-URI-Validator-master>python redfish-uri-validator.py --user Administrator --password superuser --rhost https://172.31.100.212:443 --openapi D:\scripts\Redfish-URI-Validator-master\openapi\openapi.yaml

response
`Opening D:\scripts\Redfish-URI-Validator-master\openapi\openapi.yaml...
redfish-uri-validator.py:46: YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as the default Loader is unsafe. Please read https://msg.pyyaml.org/load for full details.
openapi_data = yaml.load( openapi_file )
Config file 'C:\Users\CaffreyLai\AppData\Local\Programs\Python\Python37\redfish.conf' not found

Logging in to https://172.31.100.212:443...`

Please help to check.

Hi,

I try the latest code and can't log into the target with correct credential. The ERROR always shows after program ruining for a while. Please help to check.

Can we have an option to specify the location where the results will be generated?

Following Redfish spec DSP0266 1.11, session 38.1 https://www.dmtf.org/sites/default/files/standards/documents/DSP0266_1.11.2.pdf, PrivilegeRegistry may include @odata.id (optional)

and DMTF doesn’t define @odata.id for https://redfish.dmtf.org/registries/Redfish_1.1.0_PrivilegeRegistry.json. But Redfish URI Validator tool is required this property for all include PrivilegeRegistry so this is a tool issue. This opinion is confirmed by DMTF following this topic https://redfishforum.com/thread/994/odata-missing-redfish-privilegeregistry-json.
Please review and have solution for it.

Hi,

Tool doesn't have a way to skip level2 OEM resources, so will show unexpected ERRORs for OEM resources.

For example, if we have following OEM resource and show under ServiceRoot, tool will show Warning in test report and this is expected because OEM schema not included in openapi.ymal.

"Oem": { "ABC": { "@odata.type": "#ABC.v1_0_0.ABC", "ABC": { "@odata.id": "/redfish/v1/ABC" } } }

But resources under "/redfish/v1/ABC" will be reported as ERROR in report, because can't find match URI pattern in openapi.ymal, like "/redfish/v1/ABC/LogServices".

Please help to check this problem. Thank you so much.

BR,
Caffrey

I have a redfish service that represents UPI ports on a CPU. Standard schemas do not provide a way to do this, so inside a Processor resource we have:

    "Oem": {
        "Hpe": {
            "Ports": {
                "@odata.id": "<Processor URI>/Ports"

And that leads to a collection of ports, using the standard Port and PortCollection resources. These don't conform to the list of acceptable "Port" URIs, but from what I understand, that is OK if it is linked under OEM.

If a Bios resource has a @Redfish.Settings resource, with a URI like /redfish/v1/Systems/1/Bios/Settings, redfish-uri-validator will flag that as an error. But this conforms with examples in the redfish schema guide.