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

new custom field type: data rate #7004

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

Originally created by @swoga on GitHub (Sep 20, 2022).

NetBox version

v.3.3.4

Feature type

New functionality

Proposed functionality

Add a new type of custom field for data rates that use the SelectSpeedWidget for input and humanize_speed for representation in table views.

Use case

We would like to document the bandwidth for L2VPN entries, so we would create a custom field.
The widget would make it easier to enter values and the pretty formatting would greatly improve readability.

(I think adding such a field to the general L2VPN model doesn't make sense in the context of multipoint connections, hence an individual solution via a custom field.)

Database changes

none

External dependencies

none

Originally created by @swoga on GitHub (Sep 20, 2022). ### NetBox version v.3.3.4 ### Feature type New functionality ### Proposed functionality Add a new type of custom field for data rates that use the `SelectSpeedWidget` for input and `humanize_speed` for representation in table views. ### Use case We would like to document the bandwidth for L2VPN entries, so we would create a custom field. The widget would make it easier to enter values and the pretty formatting would greatly improve readability. (I think adding such a field to the general L2VPN model doesn't make sense in the context of multipoint connections, hence an individual solution via a custom field.) ### Database changes none ### External dependencies none
adam added the type: feature label 2025-12-29 19:47:41 +01:00
adam closed this issue 2025-12-29 19:47:41 +01:00
adam commented 2025-12-29 19:47:42 +01:00
Author
Owner
Copy Link

@jsenecal commented on GitHub (Sep 22, 2022):

Would a Bandwidth field make sense with the L2VPNTermination Model ?

NetBox already has somewhat similar functionality on the models for CircuitTerminations port_speed field which is optional... Perhaps this would work here as well...

@jsenecal commented on GitHub (Sep 22, 2022): Would a `Bandwidth` field make sense with the [L2VPNTermination Model](https://github.com/netbox-community/netbox/blob/develop/netbox/ipam/models/l2vpn.py#L83) ? NetBox already has somewhat similar functionality on the models for [CircuitTerminations `port_speed` field](https://github.com/netbox-community/netbox/blob/develop/netbox/circuits/models/circuits.py#L183) which is optional... Perhaps this would work here as well...
adam commented 2025-12-29 19:47:42 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 26, 2022):

Add a new type of custom field for data rates that use the SelectSpeedWidget for input and humanize_speed for representation in table views.

I'm sorry but that's a bit too niche for custom fields, and would be very difficult for us to maintain long-term. You'll have to stick with a normal integer field, or as @jsenecal suggests perhaps propose adding a built-in field for this purpose.

@jeremystretch commented on GitHub (Sep 26, 2022): > Add a new type of custom field for data rates that use the SelectSpeedWidget for input and humanize_speed for representation in table views. I'm sorry but that's a bit too niche for custom fields, and would be very difficult for us to maintain long-term. You'll have to stick with a normal integer field, or as @jsenecal suggests perhaps propose adding a built-in field for this purpose.
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#7004
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?