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

Allow images to be attached to Modules and Module Types #6198

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

Originally created by @jcollie on GitHub (Mar 10, 2022).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

netbox-9959f6cd8-pzbbx (v3.2.0-beta2)

Feature type

New functionality

Proposed functionality

Allow images to be attached to modules and module types.

Use case

Having images of modules will help users identify modules.

Database changes

Lists of images will need to be added to modules and module types.

External dependencies

No response

Originally created by @jcollie on GitHub (Mar 10, 2022). Originally assigned to: @jeremystretch on GitHub. ### NetBox version netbox-9959f6cd8-pzbbx (v3.2.0-beta2) ### Feature type New functionality ### Proposed functionality Allow images to be attached to modules and module types. ### Use case Having images of modules will help users identify modules. ### Database changes Lists of images will need to be added to modules and module types. ### External dependencies _No response_
adam added the status: acceptedtype: featurebeta labels 2025-12-29 19:37:56 +01:00
adam closed this issue 2025-12-29 19:37:56 +01:00
adam commented 2025-12-29 19:37:56 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 14, 2022):

I think module types makes sense, but why modules?

@jeremystretch commented on GitHub (Mar 14, 2022): I think module types makes sense, but why modules?
adam commented 2025-12-29 19:37:57 +01:00
Author
Owner
Copy Link

@jcollie commented on GitHub (Mar 14, 2022):

Allowing on module is mostly for completeness I guess, based on device type/device. It would be good for documenting the installation of a specific module (maybe there are switches on the module that need to be configured in a certain way). It also just occurred to me that it would be good to be able to attach images to device types other than the front/rear images. That would be good for devices that aren't really rack mountable or for attaching documentation about a device type.

@jcollie commented on GitHub (Mar 14, 2022): Allowing on module is mostly for completeness I guess, based on device type/device. It would be good for documenting the installation of a specific module (maybe there are switches on the module that need to be configured in a certain way). It also just occurred to me that it would be good to be able to attach images to device types other than the front/rear images. That would be good for devices that aren't really rack mountable or for attaching documentation about a device type.
adam commented 2025-12-29 19:37:57 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 21, 2022):

Wouldn't it make more sense to attach any images to the parent device, rather than to a specific module?

@jeremystretch commented on GitHub (Mar 21, 2022): Wouldn't it make more sense to attach any images to the parent device, rather than to a specific module?
adam commented 2025-12-29 19:37:57 +01:00
Author
Owner
Copy Link

@jcollie commented on GitHub (Mar 21, 2022):

For an installed module images from the parent device would be OK. However, it would still be nice to attach an image to the module type so that you can say "this is what X looks like" without having to do a web search for it (which can sometimes fail or be ambiguous, depending on the obscurity of the particular module).

@jcollie commented on GitHub (Mar 21, 2022): For an installed module images from the parent device would be OK. However, it would still be nice to attach an image to the module type so that you can say "this is what X looks like" without having to do a web search for it (which can sometimes fail or be ambiguous, depending on the obscurity of the particular module).
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 beta status: accepted 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#6198
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?