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

Establish a central registry for tracking the application of features (e.g. webhooks, custom links) to models #3480

New Issue
Closed
opened 2025-12-29 18:29:26 +01:00 by adam · 0 comments
adam commented 2025-12-29 18:29:26 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Mar 13, 2020).

Proposed Changes

Establish an internal registry to use for tracking which models within NetBox support which features. This should be similar in nature to the way Django registers models for its admin site. (Currently, this is accomplished through the use of several constants which each define a QuerySet filter returning the appropriate models.)

This proposal does NOT effect any changes to the assignment of these features. It is an internal change only.

Justification

Employing a central registry obviates the need to maintain explicit lists of models and simplifies the registration process. We could use a decorator, such as:

@register('webhooks', 'custom_links')
class Foo(models.model):
    ...
Originally created by @jeremystretch on GitHub (Mar 13, 2020). ### Proposed Changes Establish an internal registry to use for tracking which models within NetBox support which features. This should be similar in nature to the way Django registers models for its admin site. (Currently, this is accomplished through the use of several constants which each define a QuerySet filter returning the appropriate models.) This proposal does NOT effect any changes to the assignment of these features. It is an internal change only. ### Justification Employing a central registry obviates the need to maintain explicit lists of models and simplifies the registration process. We could use a decorator, such as: ```python @register('webhooks', 'custom_links') class Foo(models.model): ... ```
adam added the status: acceptedtype: housekeeping labels 2025-12-29 18:29:26 +01:00
adam closed this issue 2025-12-29 18:29:26 +01:00
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: housekeeping
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#3480
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?