The service /v1/provide-list-of-actual-device-equipment returns on data from the Cache, derived as follows:
ElasticSearch://control-construct={mountName}?fields=top-level-equipment;equipment(uuid;actual-equipment(manufactured-thing(equipment-type(type-name))))
I tried running a responseBody completeness test in the lab, where the responseBody is compared to the responseSchema.
The required property equipment-type-name of actual-equipment-list sometimes is missing, therefore the testcase fails (which is not actually an MWDI issue).
The OAS lists this attribute as required. As this is a convenience server and not a ressource path, MWDI should not just return what is see's in the cache 1:1. Instead MWDI implementation should be modified as follows:
return all attributes listed as required in the responseSchema
if found in the CC fill the attribute with the found value
if an attribute is missing in the CC, it will still be included, but with an empty string as value
(If required the description in the OAS could be extended to reflect that requirement more clearly (with own issue), this would be done with milestone v1.1.3_spec.)
The service
/v1/provide-list-of-actual-device-equipment
returns on data from the Cache, derived as follows:ElasticSearch://control-construct={mountName}?fields=top-level-equipment;equipment(uuid;actual-equipment(manufactured-thing(equipment-type(type-name))))
I tried running a responseBody completeness test in the lab, where the responseBody is compared to the responseSchema. The required property equipment-type-name of actual-equipment-list sometimes is missing, therefore the testcase fails (which is not actually an MWDI issue).
See example for mount-name: 513559991A
For SFP-1.4 there is no equipment-type-name.
The OAS lists this attribute as required. As this is a convenience server and not a ressource path, MWDI should not just return what is see's in the cache 1:1. Instead MWDI implementation should be modified as follows:
(If required the description in the OAS could be extended to reflect that requirement more clearly (with own issue), this would be done with milestone v1.1.3_spec.)