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

Ability to create "role-groups" #6618

New Issue
Closed
opened 2025-12-29 19:43:11 +01:00 by adam · 4 comments
adam commented 2025-12-29 19:43:11 +01:00
Owner
Copy Link

Originally created by @AnthoBalitrand on GitHub (Jul 1, 2022).

NetBox version

v3.2.5

Feature type

Data model extension

Proposed functionality

Add the ability to create "role-groups" to bundle several roles.

Use case

It would help to keep a good granularity in the roles assigned to the devices, while being able to bundle them if we have to match a lot of roles in config contexts.

Database changes

No response

External dependencies

No response

Originally created by @AnthoBalitrand on GitHub (Jul 1, 2022). ### NetBox version v3.2.5 ### Feature type Data model extension ### Proposed functionality Add the ability to create "role-groups" to bundle several roles. ### Use case It would help to keep a good granularity in the roles assigned to the devices, while being able to bundle them if we have to match a lot of roles in config contexts. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 19:43:11 +01:00
adam closed this issue 2025-12-29 19:43:11 +01:00
adam commented 2025-12-29 19:43:12 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 27, 2022):

Add the ability to create "role-groups" to bundle several roles.

Is the proposal here to introduce a new model to represent groups of roles, or to make the existing model(s) self-nesting?

Consider the following pretend hierarchy of device roles:

  • Switch
    • Access switch
    • Distribution switch
    • Core switch
  • Router
    • Edge router
    • Branch router
  • Firewall

In this example, would Switch, Router, and Firewall be assignable as device roles, or would only their children be assignable?

@jeremystretch commented on GitHub (Jul 27, 2022): > Add the ability to create "role-groups" to bundle several roles. Is the proposal here to introduce a _new_ model to represent groups of roles, or to make the existing model(s) self-nesting? Consider the following pretend hierarchy of device roles: * Switch * Access switch * Distribution switch * Core switch * Router * Edge router * Branch router * Firewall In this example, would Switch, Router, and Firewall be assignable as device roles, or would only their children be assignable?
adam commented 2025-12-29 19:43:12 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 27, 2022):

Actually, this seems like a duplicate of #6290.

@jeremystretch commented on GitHub (Jul 27, 2022): Actually, this seems like a duplicate of #6290.
adam commented 2025-12-29 19:43:12 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Aug 2, 2022):

I would concur and I would almost say that #6290 is the preferred implementation anyways.

@DanSheps commented on GitHub (Aug 2, 2022): I would concur and I would almost say that #6290 is the preferred implementation anyways.
adam commented 2025-12-29 19:43:13 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 3, 2022):

Agreed; let's role this into #6290. That FR is currently blocked pending investigation into a potential replacement for django-mptt.

@jeremystretch commented on GitHub (Aug 3, 2022): Agreed; let's role this into #6290. That FR is currently blocked pending investigation into a potential replacement for django-mptt.
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#6618
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?