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

RADb Integration #1119

New Issue
Closed
opened 2025-12-29 16:29:09 +01:00 by adam · 8 comments
adam commented 2025-12-29 16:29:09 +01:00
Owner
Copy Link

Originally created by @bellwood on GitHub (Jul 20, 2017).

Issue type:
Feature Request

RADb has announced beta API support for their IRR service.

The following link contains all the details and usage examples:

http://radb.net/support/api.php

I'm not 100% on how the integration might work or look but we'd need to bring AS numbers into the mix at the Aggregate/Prefix/Provider level to properly do it and glue it all together - expanding on #127 perhaps

Originally created by @bellwood on GitHub (Jul 20, 2017). **Issue type:** Feature Request RADb has announced beta API support for their IRR service. The following link contains all the details and usage examples: http://radb.net/support/api.php I'm not 100% on how the integration might work or look but we'd need to bring AS numbers into the mix at the Aggregate/Prefix/Provider level to properly do it and glue it all together - expanding on #127 perhaps
adam closed this issue 2025-12-29 16:29:09 +01:00
adam commented 2025-12-29 16:29:10 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 24, 2017):

Sounds neat, but this needs to be fleshed out more. How we'll need to extend the data model, what the workflow will look like, etc.

@jeremystretch commented on GitHub (Jul 24, 2017): Sounds neat, but this needs to be fleshed out more. How we'll need to extend the data model, what the workflow will look like, etc.
adam commented 2025-12-29 16:29:10 +01:00
Author
Owner
Copy Link

@bellwood commented on GitHub (Jul 26, 2017):

I'll dedicate some thought cycles to this and try to have something useful to share next week

@bellwood commented on GitHub (Jul 26, 2017): I'll dedicate some thought cycles to this and try to have something useful to share next week
adam commented 2025-12-29 16:29:10 +01:00
Author
Owner
Copy Link

@ktims commented on GitHub (Jul 26, 2017):

RIPE also has an API for the same functionality, and you don't have to pay them to use their IRR: https://github.com/RIPE-NCC/whois/wiki/WHOIS-REST-API

Some thought should be put into generalizing whatever interface is designed.

@ktims commented on GitHub (Jul 26, 2017): RIPE also has an API for the same functionality, and you don't have to pay them to use their IRR: https://github.com/RIPE-NCC/whois/wiki/WHOIS-REST-API Some thought should be put into generalizing whatever interface is designed.
adam commented 2025-12-29 16:29:10 +01:00
Author
Owner
Copy Link

@bellwood commented on GitHub (Jul 26, 2017):

@ktims funny you mention that as the RADb API was modeled to be nearly the same as RIPE's - they state it on their API page:

The API is similar to the RIPE API (see https://github.com/RIPE-NCC/whois/wiki/WHOIS-REST-API-WhoisResources)

So supporting both shouldn't too much of a burden =)

@bellwood commented on GitHub (Jul 26, 2017): @ktims funny you mention that as the RADb API was modeled to be nearly the same as RIPE's - they state it on their API page: > The API is similar to the RIPE API (see https://github.com/RIPE-NCC/whois/wiki/WHOIS-REST-API-WhoisResources) So supporting both shouldn't too much of a burden =)
adam commented 2025-12-29 16:29:11 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 26, 2018):

I have to close this out since it seems to have stagnated. However, feel free to submit a fresh FR with a detailed description, use case, etc. if you're still interested in working on it.

@jeremystretch commented on GitHub (Jan 26, 2018): I have to close this out since it seems to have stagnated. However, feel free to submit a fresh FR with a detailed description, use case, etc. if you're still interested in working on it.
adam commented 2025-12-29 16:29:11 +01:00
Author
Owner
Copy Link

@bellwood commented on GitHub (Jan 26, 2018):

Respectfully, FR’s are stagnating as core FR from 18+ months ago are getting no attention and there’s seemingly no clear path for where Netbox is going.

I’m all for seeing new functionality but if the basics the masses are asking for or other product-killer features have had no input from you in 18+ months the community won’t be engaged to keep these FR “fresh”.

Thanks 🙏🏻

@bellwood commented on GitHub (Jan 26, 2018): Respectfully, FR’s are stagnating as core FR from 18+ months ago are getting no attention and there’s seemingly no clear path for where Netbox is going. I’m all for seeing new functionality but if the basics the masses are asking for or other product-killer features have had no input from you in 18+ months the community won’t be engaged to keep these FR “fresh”. Thanks 🙏🏻
adam commented 2025-12-29 16:29:11 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 26, 2018):

@bellwood The issue here is that this FR was never fleshed out to describe the proposed implementation; it's essentially just an observation that RADb has an API, which isn't actionable. The other FRs you refer to all have at least some high-level discussion of the proposed functionality. You're welcome to submit a new issue but it needs to describe what the proposed feature is, who would use it and why, what the workflow looks like, and so on.

@jeremystretch commented on GitHub (Jan 26, 2018): @bellwood The issue here is that this FR was never fleshed out to describe the proposed implementation; it's essentially just an observation that RADb has an API, which isn't actionable. The other FRs you refer to all have at least some high-level discussion of the proposed functionality. You're welcome to submit a new issue but it needs to describe what the proposed feature is, who would use it and why, what the workflow looks like, and so on.
adam commented 2025-12-29 16:29:11 +01:00
Author
Owner
Copy Link

@bellwood commented on GitHub (Jan 27, 2018):

No contest this lacks substance, simply stating my observation.

I’ll move my other input to the discussion group as that’s the appropriate place for it.

Thank you 😁

@bellwood commented on GitHub (Jan 27, 2018): No contest this lacks substance, simply stating my observation. I’ll move my other input to the discussion group as that’s the appropriate place for it. Thank you 😁
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
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#1119
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?