You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I noticed that for all PUT, POST and PATCH API endpoints that support Custom_fields, the parameter custom_fields in the body is defined as a string instead of an object (AKA dict)
See below an example for POST /api/circuits/circuits/ captured from /api/docs/?format=openapi
I can confirm that with netbox 2.3.2, the swagger file contains custom_fields as object for the endpoint /api/circuits/circuits/ and not as string as described above.
Issue type
[ ] Feature request
[X ] Bug report
[ ] Documentation
Environment
Description
I noticed that for all PUT, POST and PATCH API endpoints that support Custom_fields, the parameter
custom_fields
in the body is defined as astring
instead of an object (AKA dict)See below an example for
POST /api/circuits/circuits/
captured from/api/docs/?format=openapi
Here is the full list of path that have the issue as far as I can tell
The text was updated successfully, but these errors were encountered: