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

Documentation: "Administration / Replicating NetBox" cache invalidation doesn't work as stated #5360

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

Originally created by @cs-1 on GitHub (Sep 13, 2021).

Originally assigned to: @jeremystretch on GitHub.

Change Type

Correction

Area

Administration/development

Proposed Changes

The current "Replicating NetBox" documentation says that the cache of the source machine should be invalidated first before moving NetBox data to a different machine by issueing

# source /opt/netbox/venv/bin/activate
(venv) # python3 manage.py invalidate all

However, the "invalidate" command for "manage.py" doesn't exist anymore in NetBox v3.0.2. Running the latter command yields

Unknown command: 'invalidate'
Type 'manage.py help' for usage.

The documentation should be changed to either contain the new command for invalidating the cache or -- if cache invalidation isn't necessary anymore -- the section about cache invalidation should be removed.

Originally created by @cs-1 on GitHub (Sep 13, 2021). Originally assigned to: @jeremystretch on GitHub. ### Change Type Correction ### Area Administration/development ### Proposed Changes The current "Replicating NetBox" documentation says that the cache of the source machine should be invalidated first before moving NetBox data to a different machine by issueing ``` # source /opt/netbox/venv/bin/activate (venv) # python3 manage.py invalidate all ``` However, the "invalidate" command for "manage.py" doesn't exist anymore in NetBox v3.0.2. Running the latter command yields ``` Unknown command: 'invalidate' Type 'manage.py help' for usage. ``` The documentation should be changed to either contain the new command for invalidating the cache or -- if cache invalidation isn't necessary anymore -- the section about cache invalidation should be removed.
adam added the status: acceptedtype: documentation labels 2025-12-29 19:27:08 +01:00
adam closed this issue 2025-12-29 19:27:08 +01:00
adam commented 2025-12-29 19:27:08 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 13, 2021):

Queryset caching was removed under #6639 in v3.0. Looks like this bit in the documentation was missed.

@jeremystretch commented on GitHub (Sep 13, 2021): Queryset caching was removed under #6639 in v3.0. Looks like this bit in the documentation was missed.
adam commented 2025-12-29 19:27:08 +01:00
Author
Owner
Copy Link

@cs-1 commented on GitHub (Sep 13, 2021):

Thanks for the info and for looking into this.

@cs-1 commented on GitHub (Sep 13, 2021): Thanks for the info and for looking into this.
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: documentation
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#5360
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?