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 disable media upload #7043

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

Originally created by @ITJamie on GitHub (Sep 28, 2022).

NetBox version

v3.3.4

Feature type

Change to existing functionality

Proposed functionality

A configuration option to disable media/image upload.

Use case

We would prefer our staff to upload images to our cloud drive product and use embedded image urls in netbox comments / markdown.
It allows us to keep our "site" files together and not have some in netbox, some in cloud drive etc.

While its technically possible to use the django permission to disable "extra image attachment" this does not apply to superadmins. we would just like to fully disable it.

Database changes

No response

External dependencies

No response

Originally created by @ITJamie on GitHub (Sep 28, 2022). ### NetBox version v3.3.4 ### Feature type Change to existing functionality ### Proposed functionality A configuration option to disable media/image upload. ### Use case We would prefer our staff to upload images to our cloud drive product and use embedded image urls in netbox comments / markdown. It allows us to keep our "site" files together and not have some in netbox, some in cloud drive etc. While its technically possible to use the django permission to disable "extra image attachment" this does not apply to superadmins. we would just like to fully disable it. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurepending closurestatus: under review labels 2025-12-29 19:48:16 +01:00
adam closed this issue 2025-12-29 19:48:16 +01:00
adam commented 2025-12-29 19:48:17 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 29, 2022):

Disabling storage overall seems likely to break things in unanticipated ways. I'm not sure I'm comfortable taking on that risk to satisfy what I assume is a fairly niche use case.

It's also worth pointing out that this would disable the use of device type images, and any other such fields that NetBox may introduce in future releases, in addition to image attachments.

While its technically possible to use the django permission to disable "extra image attachment" this does not apply to superadmins. we would just like to fully disable it.

Shouldn't superusers know better? 🙂

@jeremystretch commented on GitHub (Sep 29, 2022): Disabling storage overall seems likely to break things in unanticipated ways. I'm not sure I'm comfortable taking on that risk to satisfy what I assume is a fairly niche use case. It's also worth pointing out that this would disable the use of device type images, and any other such fields that NetBox may introduce in future releases, in addition to image attachments. > While its technically possible to use the django permission to disable "extra image attachment" this does not apply to superadmins. we would just like to fully disable it. Shouldn't superusers know better? :slightly_smiling_face:
adam commented 2025-12-29 19:48:17 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Dec 3, 2022):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Dec 3, 2022): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:48:17 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jan 2, 2023):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Jan 2, 2023): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure status: under review 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#7043
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?