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

Store the last or historic configuration files of the devices #3790

New Issue
Closed
opened 2025-12-29 18:31:14 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:31:14 +01:00
Owner
Copy Link

Originally created by @enribla on GitHub (Jun 16, 2020).

Environment

  • Python version: 3.7.4
  • NetBox version: 2.8.0

Getting the configuration of a device in is not very useful for the network engineers in my opinion because there are two things:

  • If the device is broken you can access to it
  • It takes too long ans we stablish an ssh conection each time

In my opinion it should be much practical to store the config file and get this file and have the possibility to generate a new config file and get track of them with the date

Each time that we want to read the config of a device we need to wait too long so finally its better to go to the linux server where I store the backups and do a 'cat'
In case the router is broken we can't get here the backup file

Yes it should create a link to a file. These backup files could be stored in a special folder that we even could populate externally. (same name of the device with a pattern)

Nothing in particular

Originally created by @enribla on GitHub (Jun 16, 2020). <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/forum/#!forum/netbox-discuss NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.7.4 * NetBox version: 2.8.0 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> Getting the configuration of a device in is not very useful for the network engineers in my opinion because there are two things: - If the device is broken you can access to it - It takes too long ans we stablish an ssh conection each time In my opinion it should be much practical to store the config file and get this file and have the possibility to generate a new config file and get track of them with the date <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> Each time that we want to read the config of a device we need to wait too long so finally its better to go to the linux server where I store the backups and do a 'cat' In case the router is broken we can't get here the backup file <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> Yes it should create a link to a file. These backup files could be stored in a special folder that we even could populate externally. (same name of the device with a pattern) <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> Nothing in particular
adam closed this issue 2025-12-29 18:31:14 +01:00
adam commented 2025-12-29 18:31:14 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 16, 2020):

This is out of scope for NetBox, and there are plenty of tools already which do this.

@jeremystretch commented on GitHub (Jun 16, 2020): This is out of scope for NetBox, and there are plenty of tools already which do 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
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#3790
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?