starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-12 05:20:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Permit KMZ/KML attachments on circuits? #1853

New Issue
Closed
opened 2025-12-29 17:19:49 +01:00 by adam · 3 comments
adam commented 2025-12-29 17:19:49 +01:00
Owner
Copy Link

Originally created by @bellwood on GitHub (Jul 19, 2018).

Issue type

[X] Feature request

Environment

  • Python version: 3.6.6
  • NetBox version: 2.3.5

Description

Similar to other attachments but permit/allow attaching KMZ/KML files for circuits.

These files show the actual path a circuit (Fiber, etc) would traverse geographically in Google Earth. Most carriers will provide their ISP customers with these for mapping/diversity/build purposes.

KML is essentially XML:
https://googlemaps.github.io/kml-samples/interactive/index.html

Edit: clarified Carrier/ISP

Originally created by @bellwood on GitHub (Jul 19, 2018). ### Issue type [X] Feature request ### Environment * Python version: 3.6.6 * NetBox version: 2.3.5 ### Description Similar to other attachments but permit/allow attaching KMZ/KML files for circuits. These files show the actual path a circuit (Fiber, etc) would traverse geographically in Google Earth. Most carriers will provide their ISP customers with these for mapping/diversity/build purposes. KML is essentially XML: https://googlemaps.github.io/kml-samples/interactive/index.html Edit: clarified Carrier/ISP
adam closed this issue 2025-12-29 17:19:49 +01:00
adam commented 2025-12-29 17:19:49 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 23, 2018):

I really want to avoid attaching miscellaneous files to objects in NetBox, which isn't really suitable as a document store. An alternative approach would be to link to the file(s) hosted elsewhere using a custom field on the circuit object. #969 would even allow for the use of a templatized link.

@jeremystretch commented on GitHub (Jul 23, 2018): I really want to avoid attaching miscellaneous files to objects in NetBox, which isn't really suitable as a document store. An alternative approach would be to link to the file(s) hosted elsewhere using a custom field on the circuit object. #969 would even allow for the use of a templatized link.
adam commented 2025-12-29 17:19:49 +01:00
Author
Owner
Copy Link

@bellwood commented on GitHub (Jul 23, 2018):

The issue there is storing confidential/proprietary/protected information on a third-party system could/would be in violation of SOC.

Given that a KMZ/KML is directly related 1:1 on a circuit its hardly miscellaneous, its the "source of truth" for a circuit.

Just my .02 but Netbox would be more attractive if it had some additional convenience functions that would help me as an IT administrator reduce the number of programs/systems I need to have.

Not saying Netbox needs to be a bloated beast, but, for those of us who are under strict and tight audit/compliance guidelines reducing the number of in-scope systems makes our lives so much easier and Netbox has the potential to do that.

@bellwood commented on GitHub (Jul 23, 2018): The issue there is storing confidential/proprietary/protected information on a third-party system could/would be in violation of SOC. Given that a KMZ/KML is directly related 1:1 on a circuit its hardly miscellaneous, its the "source of truth" for a circuit. Just my .02 but Netbox would be more attractive if it had some additional convenience functions that would help me as an IT administrator reduce the number of programs/systems I need to have. Not saying Netbox needs to be a bloated beast, but, for those of us who are under strict and tight audit/compliance guidelines reducing the number of in-scope systems makes our lives so much easier and Netbox has the potential to do that.
adam commented 2025-12-29 17:19:50 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 23, 2018):

The issue there is storing confidential/proprietary/protected information on a third-party system could/would be in violation of SOC.

It wouldn't need to be a third-party system. Any file store accessible from the client accessing NetBox would work.

@jeremystretch commented on GitHub (Jul 23, 2018): > The issue there is storing confidential/proprietary/protected information on a third-party system could/would be in violation of SOC. It wouldn't need to be a third-party system. Any file store accessible from the client accessing NetBox would work.
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#1853
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?