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

Document supported image types for device types & image attachments #7045

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

Originally created by @wolfspyre on GitHub (Sep 29, 2022).

NetBox version

3.3.4

Feature type

Change to existing functionality

Proposed functionality

Documentation would clearly state what image types are supported. or at least would point to upstream documentation which controls support.
This issue to add HEIC support references Django's Image Field documentation. That seems to imply Pillow is most likely the primary source for signal.... but support could be augmented elsewhere. Regardless, having it documented what image types are the user can expect to use for devices would be helpful.

Use case

users wouldn't wonder if the image type they want to use is supported, and when exploring, would know whether behavior being experienced is a bug or not.

Database changes

No response

External dependencies

as stated above, it seems Django's image field and python-pillow are upstream influences to this. I'm not sure if there are others.

Originally created by @wolfspyre on GitHub (Sep 29, 2022). ### NetBox version 3.3.4 ### Feature type Change to existing functionality ### Proposed functionality Documentation would clearly state what image types are supported. or at least would point to upstream documentation which controls support. [This issue to add HEIC support](https://github.com/netbox-community/netbox/issues/9410) references [Django's Image Field](https://docs.djangoproject.com/en/4.1/ref/models/fields/#imagefield) documentation. That seems to imply [Pillow](https://github.com/python-pillow/Pillow) is most likely the primary source for signal.... but support could be augmented elsewhere. Regardless, having it documented what image types are the user can expect to use for devices would be helpful. ### Use case users wouldn't wonder if the image type they want to use is supported, and when exploring, would know whether behavior being experienced is a bug or not. ### Database changes _No response_ ### External dependencies as stated above, it seems [Django's image field](https://docs.djangoproject.com/en/4.1/ref/models/fields/#imagefield) and [python-pillow](https://github.com/python-pillow/Pillow) are upstream influences to this. I'm not sure if there are others.
adam added the type: featurestatus: needs ownerpending closure labels 2025-12-29 19:48:18 +01:00
adam closed this issue 2025-12-29 19:48:18 +01:00
adam commented 2025-12-29 19:48:19 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Nov 29, 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 (Nov 29, 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:19 +01:00
Author
Owner
Copy Link

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

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 (Dec 29, 2022): 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: needs owner 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#7045
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?