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

Extend Image Attachments to DeviceTypes #1199

New Issue
Closed
opened 2025-12-29 16:29:59 +01:00 by adam · 5 comments
adam commented 2025-12-29 16:29:59 +01:00
Owner
Copy Link

Originally created by @wenners on GitHub (Aug 25, 2017).

Issue type

[x] Feature request
[ ] Bug report
[ ] Documentation

Environment

  • Python version: 3.4.5
  • NetBox version: 2.1.3

Description

A detailed description of the proposed functionality

Expand the added fuctionality of #152. Also DeviceTyes should have the ability to attach images.

A use case for the new feature

IMHO it is very useful to attach also images to DeviceTypes. We usually store a stock picture of servers, switches, line cards, etc. to have clarity about available interfaces and ports. Having this feature only at Device level we would need to attach these same pictures to every device so I think it makes more sense to attach it at DeviceType level.

A rough description of any necessary changes to the database schema

No change needed, DB schema was already changed with #152, it only needs to be extended to DeviceType.

Any relevant third-party libraries which would be needed

Same as before.

Originally created by @wenners on GitHub (Aug 25, 2017). ### Issue type [x] Feature request <!-- Requesting the implementation of a new feature --> [ ] Bug report <!-- Reporting unexpected or erroneous behavior --> [ ] Documentation <!-- Proposing a modification to the documentation --> ### Environment * Python version: 3.4.5 * NetBox version: 2.1.3 ### Description #### A detailed description of the proposed functionality Expand the added fuctionality of #152. Also DeviceTyes should have the ability to attach images. #### A use case for the new feature IMHO it is very useful to attach also images to DeviceTypes. We usually store a stock picture of servers, switches, line cards, etc. to have clarity about available interfaces and ports. Having this feature only at Device level we would need to attach these same pictures to every device so I think it makes more sense to attach it at DeviceType level. #### A rough description of any necessary changes to the database schema No change needed, DB schema was already changed with #152, it only needs to be extended to DeviceType. #### Any relevant third-party libraries which would be needed Same as before.
adam closed this issue 2025-12-29 16:29:59 +01:00
adam commented 2025-12-29 16:30:00 +01:00
Author
Owner
Copy Link

@InsaneSplash commented on GitHub (Aug 28, 2017):

I'd also like to propose that Image Attachments can be extended to Tenants. This would allow us to attach a network diagram for the customer, as an overview of all sites. This assists in seeing the big picture of the customers overall infrastructure and useful for reference in the future.

@InsaneSplash commented on GitHub (Aug 28, 2017): I'd also like to propose that Image Attachments can be extended to Tenants. This would allow us to attach a network diagram for the customer, as an overview of all sites. This assists in seeing the big picture of the customers overall infrastructure and useful for reference in the future.
adam commented 2025-12-29 16:30:00 +01:00
Author
Owner
Copy Link

@lae commented on GitHub (Aug 28, 2017):

PDF attachments for device types would be useful as well for storing documents like specification sheets and administration guides (came here to request this actually).

@lae commented on GitHub (Aug 28, 2017): PDF attachments for device types would be useful as well for storing documents like specification sheets and administration guides (came here to request this actually).
adam commented 2025-12-29 16:30:00 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 29, 2017):

@lae I've added a section to the FAQ to address this since it keeps coming up.

@jeremystretch commented on GitHub (Aug 29, 2017): @lae I've [added a section to the FAQ](https://github.com/digitalocean/netbox/wiki/Frequently-Asked-Questions#user-content-why-does-netbox-support-only-image-attachments) to address this since it keeps coming up.
adam commented 2025-12-29 16:30:00 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 29, 2017):

The goal of supporting the attachment of images to sites, racks, and devices is to enable photographic documentation of a user's particular installation. Since device types are typically not unique to a specific organization (e.g. everyone who owns a Juniper EX4300-48T has the exact same hardware), there should not be a need to store photos of them in NetBox. Instead, you can link to the manufacturer's documentation, or to photos stored elsewhere if you really want to.

@jeremystretch commented on GitHub (Aug 29, 2017): The goal of supporting the attachment of images to sites, racks, and devices is to enable photographic documentation of a user's particular installation. Since device types are typically not unique to a specific organization (e.g. everyone who owns a Juniper EX4300-48T has the exact same hardware), there should not be a need to store photos of them in NetBox. Instead, you can link to the manufacturer's documentation, or to photos stored elsewhere if you really want to.
adam commented 2025-12-29 16:30:01 +01:00
Author
Owner
Copy Link

@wenners commented on GitHub (Aug 30, 2017):

Ok - understood.

@wenners commented on GitHub (Aug 30, 2017): Ok - understood.
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
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#1199
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?