|
Post by jyundt on Jun 23, 2022 16:15:11 GMT
What is the expected behavior for a missing (or invalid) Resource in an interop profile? Should a missing or invalid Resource result in some sort of Fail? As an example, this profile provides as Pass as expected: { "SchemaDefinition": "RedfishInteroperabilityProfile.v1_5_0", "ProfileName": "test", "ProfileVersion": "0.0.1", "Resources": { "Chassis": { "ReadRequirement": "Mandatory", "MinVersion": "1.0.1" } } }
 However, if I list a Resource that is not present, I'm not getting any type of Fail. Example: { "SchemaDefinition": "RedfishInteroperabilityProfile.v1_5_0", "ProfileName": "test", "ProfileVersion": "0.0.1", "Resources": { "FOO": { "ReadRequirement": "Mandatory", "MinVersion": "1.0.1" } } }

|
|
|
Post by mraineri on Jun 23, 2022 18:44:40 GMT
I would expect that to produce a failure. With the way profiles are intended to be designed, we want to allow for the flexibility that resources from third parties can have requirements defined. So, while "FOO" is not found in DSP8010, another organization (like SNIA or OCP) might have a resource called "FOO" and would like to allow users to specify requirements against it.
|
|
|
Post by jyundt on Jun 23, 2022 18:48:19 GMT
Ah got it, thanks for the clarification. Because this isn't throwing a Fail, does this mean I'm hitting a bug?
|
|
|
Post by mraineri on Jun 23, 2022 18:57:24 GMT
Yes, please file an issue in GitHub for this.
|
|
|
Post by jyundt on Jun 23, 2022 19:12:38 GMT
|
|