Skip to content

API returns JSON custom field as string on certian ipam.prefix entries #16328

@FliesLikeABrick

Description

@FliesLikeABrick

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


>>> for prefix in pynetbox_instance.ipam.prefixes.filter('10.30.15'):
...   print(f"{prefix} custom_fields['references'] type: {type(prefix.custom_fields['references'])}")
... 
10.30.150.0/24 custom_fields['references'] type: <class 'dict'>
10.30.151.0/24 custom_fields['references'] type: <class '**str**'>
2606:ae80:1415:150::/64 custom_fields['references'] type: <class 'dict'>
2606:ae80:1415:151::/64 custom_fields['references'] type: <class 'dict'>

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions