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

Interface "reset to default" function #7087

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

Originally created by @agreusel on GitHub (Oct 6, 2022).

NetBox version

v3.3.4

Feature type

New functionality

Proposed functionality

Add a function/method to Interface type objects that can reset its state to a pre-defined default (i.e. null). The default values for these attributes could be overridden by configuring the interface attribute at the device-type level.

Access to the function could be through the Interface pane, or as a mini-button via the parent device's pane. Should also be accessible via API object manipulation.

Workflow:

  1. Interface object has a method called "reset" or "default".
  2. Running the method sets all attributes, except for name, module, device, type, speed and duplex, to their Null default value (if applicable). This should include custom_fields.
  3. If specific interface settings are defined in the parent device's device-type template, those interface attribute settings should be the default instead.

Use case

Often times, deprovisioning a port on a switch requires removing several pieces of configuration. Many vendors offer a simple command to reset an interface to its default state. A similar function for Netbox would make day-to-day port provisioning tasks simpler.

Database changes

From my understanding of how Netbox works, I don't think any database changes would be required.

External dependencies

From my understanding of how Netbox works, I don't think any external dependencies would be required.

Originally created by @agreusel on GitHub (Oct 6, 2022). ### NetBox version v3.3.4 ### Feature type New functionality ### Proposed functionality Add a function/method to Interface type objects that can reset its state to a pre-defined default (i.e. null). The default values for these attributes could be overridden by configuring the interface attribute at the device-type level. Access to the function could be through the Interface pane, or as a mini-button via the parent device's pane. Should also be accessible via API object manipulation. Workflow: 1. Interface object has a method called "reset" or "default". 2. Running the method sets all attributes, except for name, module, device, type, speed and duplex, to their Null default value (if applicable). This should include custom_fields. 3. If specific interface settings are defined in the parent device's device-type template, those interface attribute settings should be the default instead. ### Use case Often times, deprovisioning a port on a switch requires removing several pieces of configuration. Many vendors offer a simple command to reset an interface to its default state. A similar function for Netbox would make day-to-day port provisioning tasks simpler. ### Database changes From my understanding of how Netbox works, I don't think any database changes would be required. ### External dependencies From my understanding of how Netbox works, I don't think any external dependencies would be required.
adam added the type: featurepending closure labels 2025-12-29 20:19:04 +01:00
adam closed this issue 2025-12-29 20:19:04 +01:00
adam commented 2025-12-29 20:19:05 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Dec 6, 2022):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Dec 6, 2022): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:19:05 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jan 5, 2023):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Jan 5, 2023): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure type: feature
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#7087
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?