inconsistent object structure in Panorama REST API responses

tufin-platforms — Tue, 30 May 2023 11:03:21 GMT

Hello,
I would like to understand if some responses that we receive are valid (via Panorama REST APIs).
The problem is that some object fields may receive different formats for seemingly identical value types.
For example:

FQDN: Expected: { "@name": "FQDN_Test_Name", "@location": "shared", "fqdn": "test.madeup-fqdn.io" }, Unexpected: { "@name": "FQDN_Test_Name", "@loc": "shared", "@location": "shared", "fqdn": { "@loc": "shared", "text": "test.madeup-fqdn.io" } }, IP-netmask: Expected: { "@name": "H_10.111.111.111", "@location": "shared", "ip-netmask": "10.111.111.111/32" } Unexpected: { "@name": "H_10.111.111.111", "@loc": "shared", "@location": "shared", "ip-netmask": { "@loc": "shared", "text": "10.111.111.111/32" }, "description": { "@loc": "shared", "text": "IN-CCU" } },

These discrepancies are repeated over and over again on a variety of different fields and objects basically in the same way:
we usually expect a string value but receive an object.

What I would like to know is first of all is it valid from Panorama's stand point? is it considered as some sort of a corrupted data?
Can it potentially cause unexpected issues in Panorama?
Can you tell what exactly is causing these discrepancies ?

How common is to see these mismatches?

Thanks

topic inconsistent object structure in Panorama REST API responses in Panorama Discussions

inconsistent object structure in Panorama REST API responses