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

Custom Fields / Images import for Device Types #3606

New Issue
Closed
opened 2025-12-29 18:30:06 +01:00 by adam · 1 comment
adam commented 2025-12-29 18:30:06 +01:00
Owner
Copy Link

Originally created by @Sislik on GitHub (Apr 25, 2020).

Environment

  • Python version: 3.6.4
  • NetBox version: 2.8

Proposed Functionality

Allow custom fields and image location to be imported for new device types.

Use Case

I'm creating a yaml of quite lot of server types so i would like to make it properly also for future use.
Images -> Allowing yaml/json creation import of device images from http://www.visiocafe.com/ and put them in devicelibrary in git for everyone to use. Or option to have predefined use for picture based on slug name. (For example slug name proliant-dl360p-gen8 will have automatically picture proliant-dl360p-gen8-front.png and proliant-dl360p-gen-rear.png
Custom Fields -> There are basic informations for server types, which can be handy to have stored in inventory management, like number of dimm slot, maximum number of disk drives (even that this is more flexible value), number of pci slots. Also if this field would be possible to have been propagated to devices itself as that would allow changes of actual configuration -> 6 DIMM slots full, 12 SFF disks... etc.

I hope i'm not just doing something wrong as im new with NetBox, but im planning to use it for quite big enviroment :)

Database Changes

External Dependencies

Originally created by @Sislik on GitHub (Apr 25, 2020). ### Environment * Python version: 3.6.4 * NetBox version: 2.8 ### Proposed Functionality Allow custom fields and image location to be imported for new device types. ### Use Case I'm creating a yaml of quite lot of server types so i would like to make it properly also for future use. Images -> Allowing yaml/json creation import of device images from http://www.visiocafe.com/ and put them in devicelibrary in git for everyone to use. Or option to have predefined use for picture based on slug name. (For example slug name proliant-dl360p-gen8 will have automatically picture proliant-dl360p-gen8-front.png and proliant-dl360p-gen-rear.png Custom Fields -> There are basic informations for server types, which can be handy to have stored in inventory management, like number of dimm slot, maximum number of disk drives (even that this is more flexible value), number of pci slots. Also if this field would be possible to have been propagated to devices itself as that would allow changes of actual configuration -> 6 DIMM slots full, 12 SFF disks... etc. I hope i'm not just doing something wrong as im new with NetBox, but im planning to use it for quite big enviroment :) <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies
adam closed this issue 2025-12-29 18:30:06 +01:00
adam commented 2025-12-29 18:30:07 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 27, 2020):

Allowing yaml/json creation import of device images

We intentionally do not support the inclusion of image files in the device type library due to copyright issues.

There are basic informations for server types, which can be handy to have stored in inventory management

Custom fields are, by definition, custom. It would not make sense to include these in a standardized device type definition.

@jeremystretch commented on GitHub (Apr 27, 2020): > Allowing yaml/json creation import of device images We intentionally do not support the inclusion of image files in the device type library due to copyright issues. > There are basic informations for server types, which can be handy to have stored in inventory management Custom fields are, by definition, custom. It would not make sense to include these in a standardized device type definition.
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#3606
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?