Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Show Aggregate and RIR on Prefixes in API #11507

Open
ninjaix opened this issue Jan 16, 2023 · 2 comments · May be fixed by #18935
Open

Show Aggregate and RIR on Prefixes in API #11507

ninjaix opened this issue Jan 16, 2023 · 2 comments · May be fixed by #18935
Assignees
Labels
complexity: medium Requires a substantial but not unusual amount of effort to implement netbox status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Milestone

Comments

@ninjaix
Copy link

ninjaix commented Jan 16, 2023

NetBox version

v.3.4.1

Feature type

Change to existing functionality

Proposed functionality

In the API show aggregate and RIR value on get prefixes.

Use case

This would allow us easier use of updating our ARIN Networks by not having to re-enter custom fields for the Parent Network and RIR.

Database changes

This tables are already related in the Database.

External dependencies

none

@ninjaix ninjaix added the type: feature Introduction of new functionality to the application label Jan 16, 2023
@jsenecal
Copy link
Contributor

Hi @ninjaix,

Not sure how you built your workflow but, would querying aggregates first and then their subnets work for you ? This is a simple pattern that works just fine for us.

@jsenecal jsenecal added the status: under review Further discussion is needed to determine this issue's scope and/or implementation label Jan 21, 2023
@github-actions
Copy link
Contributor

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 github-actions bot added the pending closure Requires immediate attention to avoid being closed for inactivity label Apr 21, 2023
@jeremystretch jeremystretch added needs milestone Awaiting prioritization for inclusion with a future NetBox release and removed status: under review Further discussion is needed to determine this issue's scope and/or implementation pending closure Requires immediate attention to avoid being closed for inactivity labels May 3, 2023
@jeremystretch jeremystretch added status: backlog Awaiting selection for work complexity: medium Requires a substantial but not unusual amount of effort to implement labels May 21, 2024
@jeremystretch jeremystretch added the netbox label Nov 1, 2024 — with Linear
@jeremystretch jeremystretch removed the needs milestone Awaiting prioritization for inclusion with a future NetBox release label Feb 20, 2025
@jeremystretch jeremystretch added this to the v4.3 milestone Feb 20, 2025
@DanSheps DanSheps self-assigned this Mar 18, 2025
@DanSheps DanSheps added status: accepted This issue has been accepted for implementation and removed status: backlog Awaiting selection for work labels Mar 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complexity: medium Requires a substantial but not unusual amount of effort to implement netbox status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants