Open Ziabatcha opened 1 week ago
We had a look at this issue. Technically speaking, the data returned by the API /v1/provide-inventory-data-of-device matches the OAS spec. The options "additionalProperties: true" provided there allow additional attributes and data structures.
Apparently, the test was not carried out on the basis of the spec itself, but rather on the example of a valid data return contained therein. However, this example is just one of many conceivable examples.
The question is which specific data subsets should be passed on from the MWDI return and which should be filtered out.
API: /v1/provide-inventory-data-of-device Mount Name :513250004 and 513250006
NDL API response is not matching with the NDL schema. "auto-negotiation-pmd-list" attribute is not available in schema. Attaching NDL API response and NDL schema spec-ltp-wire-interface.txt ndl-response-ltp-wire-interface.txt