FR: Default "undefined" types for new vendor entries #2009

Closed
opened 2025-12-29 17:21:27 +01:00 by adam · 1 comment
Owner

Originally created by @unquietwiki on GitHub (Sep 17, 2018).

Environment

  • Python version: 3.6
  • NetBox version: 2.4.4

Proposed Functionality

Default "undefined" or "to-be-defined" types for new device vendor entries.

Use Case

Most small businesses with a rack (or more), may have a mix of devices thrown together. It'd be more useful in these situations to be less verbose, and have default vendor types for use in these situations.

Database Changes

None

External Dependencies

None

Originally created by @unquietwiki on GitHub (Sep 17, 2018). ### Environment * Python version: 3.6 * NetBox version: 2.4.4 ### Proposed Functionality Default "undefined" or "to-be-defined" types for new device vendor entries. ### Use Case Most small businesses with a rack (or more), may have a mix of devices thrown together. It'd be more useful in these situations to be less verbose, and have default vendor types for use in these situations. ### Database Changes None ### External Dependencies None
adam closed this issue 2025-12-29 17:21:27 +01:00
Author
Owner

@jeremystretch commented on GitHub (Sep 18, 2018):

The NetBox data model necessitates the definition of a device type before you can add a device.

@jeremystretch commented on GitHub (Sep 18, 2018): The NetBox data model necessitates the definition of a device type before you can add a device.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#2009