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

Add a field DNS name pattern to IP Address Bulk Create #10865

New Issue
Closed
opened 2025-12-29 21:36:56 +01:00 by adam · 3 comments
adam commented 2025-12-29 21:36:56 +01:00
Owner
Copy Link

Originally created by @jhofmueller on GitHub (Mar 10, 2025).

NetBox version

v4.2.5

Feature type

New functionality

Proposed functionality

The widget for bulk creation of IP Addresses should have a field "DNS name pattern" like "Address pattern" which allows to specify a DNS name like "server[0-9].example.com". See Issue 18851.

Use case

Make creating multiple IP Addresses easier.

Database changes

No response

External dependencies

No response

Originally created by @jhofmueller on GitHub (Mar 10, 2025). ### NetBox version v4.2.5 ### Feature type New functionality ### Proposed functionality The widget for bulk creation of IP Addresses should have a field "DNS name pattern" like "Address pattern" which allows to specify a DNS name like "server[0-9].example.com". See [Issue 18851](https://github.com/netbox-community/netbox/issues/18851). ### Use case Make creating multiple IP Addresses easier. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: needs ownerpending closurecomplexity: medium labels 2025-12-29 21:36:56 +01:00
adam closed this issue 2025-12-29 21:36:56 +01:00
adam commented 2025-12-29 21:36:56 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 13, 2025):

There's a similar pattern to this right now with interfaces, where the name and label fields can be patternized in this manner. However, I'd like this work to entail collapsing the "bulk create" view for IP addresses into the regular create view, as we do for device interfaces, so that we can eliminate it as a one-off.

@jeremystretch commented on GitHub (Mar 13, 2025): There's a similar pattern to this right now with interfaces, where the `name` and `label` fields can be patternized in this manner. However, I'd like this work to entail collapsing the "bulk create" view for IP addresses into the regular create view, as we do for device interfaces, so that we can eliminate it as a one-off.
adam commented 2025-12-29 21:36:57 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 12, 2025):

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. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Jun 12, 2025): 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. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/main/CONTRIBUTING.md).
adam commented 2025-12-29 21:36:57 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jul 12, 2025):

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 (Jul 12, 2025): 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 complexity: medium pending closure status: needs owner 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#10865
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?