Duplicate/Create new device types from existing #1495

Closed
opened 2025-12-29 16:32:28 +01:00 by adam · 3 comments
Owner

Originally created by @slindermann on GitHub (Jan 17, 2018).

Issue type

[x] Feature request
[ ] Bug report
[ ] Documentation

Environment

Python version: 3.5
NetBox version: 2.2.8

Description

Hi,
I thought it would be very handy to be able to create new device types based on existing models. I'm looking for some sort of "duplicate" button that allows me to copy interfaces, device bays and console ports over to a new device type in which I only need to adjust the model name etc.

For instance, this would save some time if one needs to create a range of Juniper switch models (EX4200-48T, EX4200-48PX, ...).

Let me know if this might be an easy implementation w/o too much of an effort for you guys.

Thanks,
Simon

Originally created by @slindermann on GitHub (Jan 17, 2018). ## Issue type [x] Feature request [ ] Bug report [ ] Documentation ## Environment Python version: 3.5 NetBox version: 2.2.8 ## Description Hi, I thought it would be very handy to be able to create new device types based on existing models. I'm looking for some sort of "duplicate" button that allows me to copy interfaces, device bays and console ports over to a new device type in which I only need to adjust the model name etc. For instance, this would save some time if one needs to create a range of Juniper switch models (EX4200-48T, EX4200-48PX, ...). Let me know if this might be an easy implementation w/o too much of an effort for you guys. Thanks, Simon
adam added the status: duplicate label 2025-12-29 16:32:28 +01:00
adam closed this issue 2025-12-29 16:32:28 +01:00
Author
Owner

@zevlag commented on GitHub (Jan 17, 2018):

See #242 and #451 and #33

@zevlag commented on GitHub (Jan 17, 2018): See #242 and #451 and #33
Author
Owner

@slindermann commented on GitHub (Jan 18, 2018):

Thanks Josh, should have been looking for the "clone" keyword :)
Any ETA when #451 is going to be implemented?

@slindermann commented on GitHub (Jan 18, 2018): Thanks Josh, should have been looking for the "clone" keyword :) Any ETA when #451 is going to be implemented?
Author
Owner

@jeremystretch commented on GitHub (Jan 22, 2018):

#33 is more likely to happen soon. #451 is going to be pretty involved.

@jeremystretch commented on GitHub (Jan 22, 2018): #33 is more likely to happen soon. #451 is going to be pretty involved.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#1495