API returns JSON custom field as string on certian ipam.prefix entries #16345
Replies: 2 comments
-
The database values unsurprisingly appear to be handling this differently These are the same prefixes as listed above:
Here are the relevant prefix rows' custom_field_data, the broken prefix of 8815 has the 'references' custom field value as an escaped string instead of continuing the native JSON representation. This data has not been updated in some time (as evidenced by our 'last updated' date embedded in the data'), I believe the handling of this data changed from 3.6.3 to 3.7.7 (or a database migration was applied?)
|
Beta Was this translation helpful? Give feedback.
-
A new bug issue has been opened after we investigated and found the actions causing this corruption |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Deployment Type
Self-hosted
NetBox Version
3.7.7
Python Version
3.10
Steps to Reproduce
I do not know what preconditions led to this.
We recently upgraded from NetBox 3.6.3 to 3.7.7, and now some of our tooling is receiving unexpected string responses for fields that should be JSON. If there were prior actions taken in our data to create a precondition for this, we do not know what it was.
Expected Behavior
For a JSON-typed custom field, we expected the API to return this custom field as JSON payload instead of a string
Observed Behavior
Beta Was this translation helpful? Give feedback.
All reactions