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

Apply IPAM Role object to ASN #6298

New Issue
Closed
opened 2025-12-29 19:39:05 +01:00 by adam · 4 comments
adam commented 2025-12-29 19:39:05 +01:00
Owner
Copy Link

Originally created by @ryanmerolle on GitHub (Apr 6, 2022).

NetBox version

v3.2.0

Feature type

Data model extension

Proposed functionality

Allow users to optionally associate the IPAM role model to ASNs.

Use case

A common use case would be to assign an ASN for different uses like with peering to external internet (public ASN for a site or sites) vs internal peering using a private ASN.

Database changes

No response

External dependencies

N/A

Originally created by @ryanmerolle on GitHub (Apr 6, 2022). ### NetBox version v3.2.0 ### Feature type Data model extension ### Proposed functionality Allow users to optionally associate the IPAM role model to ASNs. ### Use case A common use case would be to assign an ASN for different uses like with peering to external internet (public ASN for a site or sites) vs internal peering using a private ASN. ### Database changes _No response_ ### External dependencies N/A
adam added the type: featurepending closurestatus: under review labels 2025-12-29 19:39:05 +01:00
adam closed this issue 2025-12-29 19:39:05 +01:00
adam commented 2025-12-29 19:39:06 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 6, 2022):

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. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Jun 6, 2022): 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. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:39:06 +01:00
Author
Owner
Copy Link

@ryanmerolle commented on GitHub (Jun 8, 2022):

This does not seem to be a major ROI item. Frankly, with custom field relationships to other objects, a user could either leverage a device role or IPAM role relationship to model the above. Happy to close this out or wait for the bot to close it.

@ryanmerolle commented on GitHub (Jun 8, 2022): This does not seem to be a major ROI item. Frankly, with custom field relationships to other objects, a user could either leverage a device role or IPAM role relationship to model the above. Happy to close this out or wait for the bot to close it.
adam commented 2025-12-29 19:39:06 +01:00
Author
Owner
Copy Link

@ryanmerolle commented on GitHub (Jul 18, 2022):

@jeremystretch if I took a stab at this, would you be cool with this added to the model?

It feels like low hanging fruit that I could apply what I learned from plugin development.

@ryanmerolle commented on GitHub (Jul 18, 2022): @jeremystretch if I took a stab at this, would you be cool with this added to the model? It feels like low hanging fruit that I could apply what I learned from plugin development.
adam commented 2025-12-29 19:39:06 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 25, 2022):

I'm going to close this out as it has not garnered any interest. It also seems like a poor fit trying to tie prefix & VLAN roles to AS number. A custom field would probably work better, and since v3.2 you can use an object-based custom field on the ASN model to achieve the same thing.

@jeremystretch commented on GitHub (Aug 25, 2022): I'm going to close this out as it has not garnered any interest. It also seems like a poor fit trying to tie prefix & VLAN roles to AS number. A custom field would probably work better, and since v3.2 you can use an [object-based custom field](https://docs.netbox.dev/en/stable/customization/custom-fields/#custom-object-fields) on the ASN model to achieve the same thing.
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 pending closure status: under review 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#6298
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?