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

Autofill VRF when adding address through prefix #4581

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

Originally created by @Lombra on GitHub (Feb 21, 2021).

Environment

  • Python version: 3.9.1
  • NetBox version: 2.10.3

Proposed Functionality

When adding a new IP address via a prefix (/ipam/prefixes/<id>/ip-addresses/) that is associated with a VRF, automatically select this VRF in the creation form. Similar to how adding devices via racks, or VLANs via VLAN groups, work.

Use Case

When adding an an address via a specific prefix, logically you would do so with the intent of having the new address in the same VRF, so autofilling this seems sane to me. Not realising the current behavior, I have done this myself a few times and ended up with addresses in the global VRF, confusing me later.

Database Changes

None.

External Dependencies

None.

Originally created by @Lombra on GitHub (Feb 21, 2021). ### Environment * Python version: 3.9.1 * NetBox version: 2.10.3 ### Proposed Functionality When adding a new IP address via a prefix (`/ipam/prefixes/<id>/ip-addresses/`) that is associated with a VRF, automatically select this VRF in the creation form. Similar to how adding devices via racks, or VLANs via VLAN groups, work. ### Use Case When adding an an address via a specific prefix, logically you would do so with the intent of having the new address in the same VRF, so autofilling this seems sane to me. Not realising the current behavior, I have done this myself a few times and ended up with addresses in the global VRF, confusing me later. <!-- 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 None. ### External Dependencies None.
adam added the status: duplicate label 2025-12-29 18:37:54 +01:00
adam closed this issue 2025-12-29 18:37:55 +01:00
adam commented 2025-12-29 18:37:55 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Feb 22, 2021):

Duplicate of #5703

@DanSheps commented on GitHub (Feb 22, 2021): Duplicate of #5703
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 status: duplicate
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#4581
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?