starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

created & last_updated fields missing from some REST API calls #5940

New Issue
Closed
opened 2025-12-29 19:34:31 +01:00 by adam · 2 comments
adam commented 2025-12-29 19:34:31 +01:00
Owner
Copy Link

Originally created by @jasonyates on GitHub (Jan 13, 2022).

Originally assigned to: @jasonyates on GitHub.

NetBox version

3.1.6-dev

Python version

3.8

Steps to Reproduce

A number of REST API calls are missing created & last_updated fields in their response. No functional impact however for parity across all API calls perhaps it would be useful to have the fields returned consistently.

Examples:
/api/dcim/virtual-chassis/
/api/dcim/cables/
/api/dcim/power-panels/
/api/dcim/rack-reservations/ (Has created but not last_updated)

Expected Behavior

created & last_updated fields are returned for all relevant objects

Observed Behavior

created & last_updated are missing some some objects

Originally created by @jasonyates on GitHub (Jan 13, 2022). Originally assigned to: @jasonyates on GitHub. ### NetBox version 3.1.6-dev ### Python version 3.8 ### Steps to Reproduce A number of REST API calls are missing created & last_updated fields in their response. No functional impact however for parity across all API calls perhaps it would be useful to have the fields returned consistently. Examples: /api/dcim/virtual-chassis/ /api/dcim/cables/ /api/dcim/power-panels/ /api/dcim/rack-reservations/ (Has created but not last_updated) ### Expected Behavior created & last_updated fields are returned for all relevant objects ### Observed Behavior created & last_updated are missing some some objects
adam added the type: bugstatus: accepted labels 2025-12-29 19:34:31 +01:00
adam closed this issue 2025-12-29 19:34:31 +01:00
adam commented 2025-12-29 19:34:32 +01:00
Author
Owner
Copy Link

@jasonyates commented on GitHub (Jan 13, 2022):

Happy to submit a PR for this.

If accepted, presumably this should be in feature not develop branch due to API changes?

@jasonyates commented on GitHub (Jan 13, 2022): Happy to submit a PR for this. If accepted, presumably this should be in feature not develop branch due to API changes?
adam commented 2025-12-29 19:34:32 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 13, 2022):

Given that it's a bug, and the fix would restore the API's intended functionality, it's fine to handle in the develop branch. (New features or functionality would need to be implemented in feature.)

Thanks for volunteering!

@jeremystretch commented on GitHub (Jan 13, 2022): Given that it's a bug, and the fix would restore the API's _intended_ functionality, it's fine to handle in the `develop` branch. (New features or functionality would need to be implemented in `feature`.) Thanks for volunteering!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label status: accepted type: bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#5940
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?