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

Storage Backend - Proxy Files #8331

New Issue
Closed
opened 2025-12-29 20:35:25 +01:00 by adam · 2 comments
adam commented 2025-12-29 20:35:25 +01:00
Owner
Copy Link

Originally created by @shepherdjay on GitHub (Jul 12, 2023).

NetBox version

v3.5.4

Feature type

Change to existing functionality

Proposed functionality

Propose changing the way external files are provided back to user when STORAGE_BACKEND is in use. Currently when attempting to retrieve an image or file that was stored into a backend (for example GCP) the URL provided for GET request back to user is the storage_backend url. For example https://storage.googleapis.com/mynetboxbucket/myimage.jpeg

Use case

Redirecting users directly to the storage backend adds complexity in permissions as not only do users require netbox permissions but they also require storage backend permissions to the bucket.

Instead if Netbox can fetch and then return the stored file to the user only netbox requires access to the bucket.

Database changes

No response

External dependencies

No response

Originally created by @shepherdjay on GitHub (Jul 12, 2023). ### NetBox version v3.5.4 ### Feature type Change to existing functionality ### Proposed functionality Propose changing the way external files are provided back to user when STORAGE_BACKEND is in use. Currently when attempting to retrieve an image or file that was stored into a backend (for example GCP) the URL provided for GET request back to user is the storage_backend url. For example `https://storage.googleapis.com/mynetboxbucket/myimage.jpeg` ### Use case Redirecting users directly to the storage backend adds complexity in permissions as not only do users require netbox permissions but they also require storage backend permissions to the bucket. Instead if Netbox can fetch and then return the stored file to the user only netbox requires access to the bucket. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: revisions needed labels 2025-12-29 20:35:25 +01:00
adam closed this issue 2025-12-29 20:35:25 +01:00
adam commented 2025-12-29 20:35:26 +01:00
Author
Owner
Copy Link

@jsenecal commented on GitHub (Jul 12, 2023):

Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our contributing guide, a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.

Furthermore, I would like to add that Storage Backends rely on third party integrations/modules and as such nothing within netbox can be done to address this feature request as formulated.

@jsenecal commented on GitHub (Jul 12, 2023): Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md), a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed. Furthermore, I would like to add that Storage Backends rely on third party integrations/modules and as such nothing within netbox can be done to address this feature request as formulated.
adam commented 2025-12-29 20:35:26 +01:00
Author
Owner
Copy Link

@shepherdjay commented on GitHub (Jul 12, 2023):

Will review as a github discussion per contributing guidlines

@shepherdjay commented on GitHub (Jul 12, 2023): Will review as a github discussion per contributing guidlines
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 status: revisions needed 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#8331
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?