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

Change status of site-related object when site is retired #7700

New Issue
Closed
opened 2025-12-29 20:27:13 +01:00 by adam · 1 comment
adam commented 2025-12-29 20:27:13 +01:00
Owner
Copy Link

Originally created by @mplanicka on GitHub (Mar 1, 2023).

NetBox version

v3.4.4

Feature type

New functionality

Proposed functionality

It would be great when site is retired, to change status of all site related objects eg. prefixes, vlans, devices etc. to deprecated (IPAM) and decommissioning/inventory (DCIM).

Use case

No need to manually change status of all site related objects after site is retired.

Database changes

none

External dependencies

none

Originally created by @mplanicka on GitHub (Mar 1, 2023). ### NetBox version v3.4.4 ### Feature type New functionality ### Proposed functionality It would be great when site is retired, to change status of all site related objects eg. prefixes, vlans, devices etc. to deprecated (IPAM) and decommissioning/inventory (DCIM). ### Use case No need to manually change status of all site related objects after site is retired. ### Database changes none ### External dependencies none
adam added the type: feature label 2025-12-29 20:27:13 +01:00
adam closed this issue 2025-12-29 20:27:14 +01:00
adam commented 2025-12-29 20:27:14 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 1, 2023):

I'm afraid this isn't something we can build into NetBox as it makes assumptions about the intended states of various objects which may or may not be applicable for a given organization or user. Instead, what you can do is write a custom script that can be used to retire a site and update its related objects according to your specific needs.

@jeremystretch commented on GitHub (Mar 1, 2023): I'm afraid this isn't something we can build into NetBox as it makes assumptions about the intended states of various objects which may or may not be applicable for a given organization or user. Instead, what you can do is write a [custom script](https://docs.netbox.dev/en/stable/customization/custom-scripts/) that can be used to retire a site and update its related objects according to your specific needs.
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 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#7700
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?