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

Ability to attach images to Circuits #4342

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

Originally created by @emajeru on GitHub (Dec 10, 2020).

Environment

  • NetBox version: v2.9.10

Proposed Functionality

When creating circuits, after defining the termination points, provide the ability to attach an image or diagram to the object, extending the functionality introduced in #152. These files will be able to be retrieved within the circuit view without needing to navigate away from the Netbox instance.

Use Case

  • Whenever value can be added by providing a geographical display of a circuit and its termination locations.
  • When there is the desire to add annotated diagrams that provide extra detail about a circuit's topology and/or configuration.

Database Changes

  • Circuit model
Originally created by @emajeru on GitHub (Dec 10, 2020). ### Environment * NetBox version: v2.9.10 ### Proposed Functionality When creating circuits, after defining the termination points, provide the ability to attach an image or diagram to the object, extending the functionality introduced in #152. These files will be able to be retrieved within the circuit view without needing to navigate away from the Netbox instance. ### Use Case * Whenever value can be added by providing a geographical display of a circuit and its termination locations. * When there is the desire to add annotated diagrams that provide extra detail about a circuit's topology and/or configuration. ### Database Changes * Circuit model
adam closed this issue 2025-12-29 18:34:59 +01:00
adam commented 2025-12-29 18:35:00 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 18, 2020):

The use cases cited sound like they're better served by a separate document store, with resources linked to from NetBox rather than stored directly.

@jeremystretch commented on GitHub (Dec 18, 2020): The use cases cited sound like they're better served by a separate document store, with resources linked to from NetBox rather than stored directly.
adam commented 2025-12-29 18:35:00 +01:00
Author
Owner
Copy Link

@emajeru commented on GitHub (Dec 18, 2020):

The use cases cited sound like they're better served by a separate document store, with resources linked to from NetBox rather than stored directly.

I agree that a seperate document store can provide the same functionality but I think the same can be said of all attachments in the Netbox UI. If a links component is added to the Circuit interface with the option to use a different MEDIA_ROOT or upload directly to an S3 bucket, the use cases can be satisfied.

@emajeru commented on GitHub (Dec 18, 2020): > The use cases cited sound like they're better served by a separate document store, with resources linked to from NetBox rather than stored directly. I agree that a seperate document store can provide the same functionality but I think the same can be said of all attachments in the Netbox UI. If a links component is added to the Circuit interface with the option to use a different MEDIA_ROOT or upload directly to an S3 bucket, the use cases can be satisfied.
adam commented 2025-12-29 18:35:00 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 21, 2020):

but I think the same can be said of all attachments in the Netbox UI.

I disagree. The image attachment is intended primarily for photographs of objects to be referenced by someone visiting the site. IMO it makes sense to store these locally within NetBox as each pertains to a specific context. Anything beyond that should be stored elsewhere. Otherwise, we'd just end up replicating a file store application within NetBox.

@jeremystretch commented on GitHub (Dec 21, 2020): > but I think the same can be said of all attachments in the Netbox UI. I disagree. The image attachment is intended primarily for photographs of objects to be referenced by someone visiting the site. IMO it makes sense to store these locally within NetBox as each pertains to a specific context. Anything beyond that should be stored elsewhere. Otherwise, we'd just end up replicating a file store application within NetBox.
adam commented 2025-12-29 18:35:01 +01:00
Author
Owner
Copy Link

@emajeru commented on GitHub (Jan 8, 2021):

Okay. I think I have a better understanding of the reasoning behind the decision.

@emajeru commented on GitHub (Jan 8, 2021): Okay. I think I have a better understanding of the reasoning behind the decision.
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#4342
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?