-
Notifications
You must be signed in to change notification settings - Fork 3k
Labels
netboxseverity: lowDoes not significantly disrupt application functionality, or a workaround is availableDoes not significantly disrupt application functionality, or a workaround is availablestatus: acceptedThis issue has been accepted for implementationThis issue has been accepted for implementationtype: bugA confirmed report of unexpected behavior in the applicationA confirmed report of unexpected behavior in the application
Description
NetBox Edition
NetBox Community
NetBox Version
v4.5.3
Python Version
3.12
Steps to Reproduce
When creating IP-related objects (Prefix, IPAddress, Aggregate, IPRange) via the REST API, read-only fields like family are unexpectedly omitted from the returned JSON response.
- Submit a
POSTrequest to create a newPrefix(e.g.,{"prefix": "192.168.0.0/24"}). - Inspect the HTTP 201 response payload.
- Note that the
familyattribute is missing from the response, even though it should be a read-only field included in the serialized output.
Expected Behavior
The API response should contain the family attribute (and any other similarly calculated fields) immediately upon object creation.
Observed Behavior
The API response is missing family attribute (and any other similarly calculated fields) immediately upon object creation.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
netboxseverity: lowDoes not significantly disrupt application functionality, or a workaround is availableDoes not significantly disrupt application functionality, or a workaround is availablestatus: acceptedThis issue has been accepted for implementationThis issue has been accepted for implementationtype: bugA confirmed report of unexpected behavior in the applicationA confirmed report of unexpected behavior in the application