starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 22:03:32 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Upload device_type images via API #5020

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

Originally created by @nyevess on GitHub (Jun 22, 2021).

NetBox version

v2.11.1

Feature type

New functionality

Proposed functionality

I suggest implement the method of upload images for device_type via API

Use case

I'm doing a big migration from OpenDCIM to Netbox, and I need migrate my device_type images via API, and I have not been able to find a way for doing this.
If this it's possible now, please let me know how to doing.
Thanks

Database changes

No response

External dependencies

No response

Originally created by @nyevess on GitHub (Jun 22, 2021). ### NetBox version v2.11.1 ### Feature type New functionality ### Proposed functionality I suggest implement the method of upload images for device_type via API ### Use case I'm doing a big migration from OpenDCIM to Netbox, and I need migrate my device_type images via API, and I have not been able to find a way for doing this. If this it's possible now, please let me know how to doing. Thanks ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurepending closurestatus: revisions needed labels 2025-12-29 19:23:14 +01:00
adam closed this issue 2025-12-29 19:23:15 +01:00
adam commented 2025-12-29 19:23:15 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 22, 2021):

I suggest implement the method of upload images for device_type via API

What specific implementation are you proposing?

@jeremystretch commented on GitHub (Jun 22, 2021): > I suggest implement the method of upload images for device_type via API What specific implementation are you proposing?
adam commented 2025-12-29 19:23:16 +01:00
Author
Owner
Copy Link

@nyevess commented on GitHub (Jun 22, 2021):

I would propose adding to the POST request, two fields:

  1. Front image
  2. Rear image
    And they will processed like the rest of the fields, codifying the image file (jpg,png,etc.) with base64 for example.
    I would clarify I'm not an expert programming and I don't know the Netbox code.
    Do you see this as possible?
    Thank you!
@nyevess commented on GitHub (Jun 22, 2021): I would propose adding to the POST request, two fields: 1. Front image 2. Rear image And they will processed like the rest of the fields, codifying the image file (jpg,png,etc.) with base64 for example. I would clarify I'm not an expert programming and I don't know the Netbox code. Do you see this as possible? Thank you!
adam commented 2025-12-29 19:23:16 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 22, 2021):

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. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Aug 22, 2021): 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. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:23:16 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 21, 2021):

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 (Sep 21, 2021): 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: 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#5020
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?