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

Include SFP module type profile by default #11467

New Issue
Closed
opened 2025-12-29 21:45:38 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:45:38 +01:00
Owner
Copy Link

Originally created by @0lini on GitHub (Aug 11, 2025).

NetBox version

v4.3.5

Feature type

Other

Proposed functionality

Since modeling SFP transciever via modules has now become best practice, it would make sense to include a default SFP transciever module type profile with each Netbox installation.

Use case

This would provide users with a framework that could be used for things like the devicetype-library.

Database changes

No response

External dependencies

No response

Originally created by @0lini on GitHub (Aug 11, 2025). ### NetBox version v4.3.5 ### Feature type Other ### Proposed functionality Since modeling SFP transciever via modules has now become best practice, it would make sense to include a default SFP transciever module type profile with each Netbox installation. ### Use case This would provide users with a framework that could be used for things like the [devicetype-library](https://github.com/netbox-community/devicetype-library). ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 21:45:38 +01:00
adam closed this issue 2025-12-29 21:45:38 +01:00
adam commented 2025-12-29 21:45:39 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 14, 2025):

We recently added one new example profile definition under FR #19571, however it was decided then that we would not continue adding more. The profiles we ship with NetBox are solely intended to provide examples; they are not meant to serve as a canonical reference in any respect. The device type library would be a more suitable home for these.

@jeremystretch commented on GitHub (Aug 14, 2025): We recently added one new example profile definition under FR #19571, however it was decided then that we would not continue adding more. The profiles we ship with NetBox are solely intended to provide examples; they are not meant to serve as a canonical reference in any respect. The device type library would be a more suitable home for these.
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#11467
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?