Allow bulk creation on netbox_device_interface_template #7044

Closed
opened 2025-12-29 19:48:16 +01:00 by adam · 1 comment
Owner

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

NetBox version

v3.2.5

Feature type

Change to existing functionality

Proposed functionality

One should be able to create interfaces in bulk using , for example, [ge,xe]-0/0/[0-9].
Right now If we use that in the name parameter, it will be created 1 single interface as literal instead of expanding for the 20 interfaces it should create when using the webui.

Use case

Add interfaces in bulk.

Database changes

No response

External dependencies

No response

Originally created by @jsalatiel on GitHub (Sep 29, 2022). ### NetBox version v3.2.5 ### Feature type Change to existing functionality ### Proposed functionality One should be able to create interfaces in bulk using , for example, [ge,xe]-0/0/[0-9]. Right now If we use that in the name parameter, it will be created 1 single interface as literal instead of expanding for the 20 interfaces it should create when using the webui. ### Use case Add interfaces in bulk. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: revisions needed labels 2025-12-29 19:48:16 +01:00
adam closed this issue 2025-12-29 19:48:17 +01:00
Author
Owner

@kkthxbye-code commented on GitHub (Sep 29, 2022):

Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our contributing guide, a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.

@kkthxbye-code commented on GitHub (Sep 29, 2022): Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md), a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#7044