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

FR: Allow images to be attached at the Tenant level #1194

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

Originally created by @traveler3468 on GitHub (Aug 24, 2017).

Issue type

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

Environment

  • Python version: 2.7
  • NetBox version: 2.1.2

Description

I will start off by saying that I have read #1039 #1408 #1416 and #969.
I will also say that I have VERY little experience with regex.

These dont quite cover what I was hoping to have. I am with you that NetBox does not need to be a file/document repository but I feel that the image attachment at the site or device level doesnt quite capture the broader picture that Im hoping to get.

By having the image attachment at the Tenant level, you could have a fantastic place to upload a network map image to show the network topology of the Tenant as a whole. I know that there is the Topology Map feature in the admin section of the site but I feel that its to restrictive. First you are only able to access the admin section if you are a superuser and, Second, the map design is limited to the hierarchical layout that is offered by the regular expression format. Third (kind of joking) who likes regular expressions anyway? Also (and this may just be my lack of knowledge or drive to learn regex) each map may not need ALL the connections displayed that a certain device has. For example if I just want to show the circuits that connect different sites and not the connections on the LAN.
Having a image attachment at the tenant level would also allow users to be able to attach the files without needing a superuser to create the map.

Originally created by @traveler3468 on GitHub (Aug 24, 2017). <!-- Before opening a new issue, please search through the existing issues to see if your topic has already been addressed. Note that you may need to remove the "is:open" filter from the search bar to include closed issues. Check the appropriate type for your issue below by placing an x between the brackets. If none of the below apply, please raise your issue for discussion on our mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please note that issues which do not fall under any of the below categories will be closed. ---> ### 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 --> <!-- Please describe the environment in which you are running NetBox. (Be sure to verify that you are running the latest stable release of NetBox before submitting a bug report.) --> ### Environment * Python version: 2.7 * NetBox version: 2.1.2 <!-- BUG REPORTS must include: * A list of the steps needed to reproduce the bug * A description of the expected behavior * Any relevant error messages (screenshots may also help) FEATURE REQUESTS must include: * A detailed description of the proposed functionality * A use case for the new feature * A rough description of any necessary changes to the database schema * Any relevant third-party libraries which would be needed --> ### Description I will start off by saying that I have read #1039 #1408 #1416 and #969. I will also say that I have VERY little experience with regex. These dont quite cover what I was hoping to have. I am with you that NetBox does not need to be a file/document repository but I feel that the image attachment at the site or device level doesnt quite capture the broader picture that Im hoping to get. By having the image attachment at the Tenant level, you could have a fantastic place to upload a network map image to show the network topology of the Tenant as a whole. I know that there is the Topology Map feature in the admin section of the site but I feel that its to restrictive. First you are only able to access the admin section if you are a superuser and, Second, the map design is limited to the hierarchical layout that is offered by the regular expression format. Third (kind of joking) who likes regular expressions anyway? Also (and this may just be my lack of knowledge or drive to learn regex) each map may not need ALL the connections displayed that a certain device has. For example if I just want to show the circuits that connect different sites and not the connections on the LAN. Having a image attachment at the tenant level would also allow users to be able to attach the files without needing a superuser to create the map.
adam closed this issue 2025-12-29 16:29:56 +01:00
adam commented 2025-12-29 16:29:56 +01:00
Author
Owner
Copy Link

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

Thank you for your interest in NetBox. We require that all issues be submitted using the template provided here. This is to ensure that only valid issues are reported and that each issue includes all the information necessary for a developer to act on it. Please update your issue so that it matches the template (this may require rewriting your issue entirely). This issue will be closed in one week if it has not been updated. Thanks!

@jeremystretch commented on GitHub (Aug 24, 2017): Thank you for your interest in NetBox. We require that all issues be submitted using the template provided [here](https://raw.githubusercontent.com/digitalocean/netbox/develop/.github/ISSUE_TEMPLATE.md). This is to ensure that only valid issues are reported and that each issue includes all the information necessary for a developer to act on it. Please update your issue so that it matches the template (this may require rewriting your issue entirely). This issue will be closed in one week if it has not been updated. Thanks!
adam commented 2025-12-29 16:29:57 +01:00
Author
Owner
Copy Link

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

This has already been addressed in the issues you referenced. Topology maps are not intended to replace traditional, detailed network diagrams, and there is no reason to store those in NetBox.

@jeremystretch commented on GitHub (Aug 24, 2017): This has already been addressed in the issues you referenced. Topology maps are not intended to replace traditional, detailed network diagrams, and there is no reason to store those in NetBox.
adam commented 2025-12-29 16:29:57 +01:00
Author
Owner
Copy Link

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

I don't see any reason not to allow images to be attached to tenants in the same way as it is exposed for sites and devices. I can think of a number of reasons why it makes sense to allow it, but ultimately it would be up to the user if its used or not.

@InsaneSplash commented on GitHub (Aug 28, 2017): I don't see any reason not to allow images to be attached to tenants in the same way as it is exposed for sites and devices. I can think of a number of reasons why it makes sense to allow it, but ultimately it would be up to the user if its used or not.
adam commented 2025-12-29 16:29:57 +01:00
Author
Owner
Copy Link

@InsaneSplash commented on GitHub (Sep 27, 2017):

I'd like to bump this, as I do think that attaching a image to a tenant is just as important as any other area. I also think this is adding flexibility to the project and the admin of their site can choose to use it.

@InsaneSplash commented on GitHub (Sep 27, 2017): I'd like to bump this, as I do think that attaching a image to a tenant is just as important as any other area. I also think this is adding flexibility to the project and the admin of their site can choose to use it.
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#1194
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?