Repository navigation
Conversation
Expanded params config for rpki server URL and backend type for query switching and lookup handling. Initial support for routinator server API endpoint.
Author
|
Fixed lint errors as detailed in workflow failures: a308534 |
Author
|
closing this as it is included in #343 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This update expands the configuration options for external RPKI validation in hyperglass. It introduces new parameters for specifying the RPKI backend type (
backend) and the RPKI server URL (rpki_server_url). These parameters allow dynamic switching between different RPKI validation providers, such as Cloudflare and Routinator, and enable custom server endpoint configuration.The
rpki_statefunction now supports both Cloudflare’s GraphQL API and Routinator’s HTTP API for RPKI validation. The backend is selected based on the provided configuration, and the appropriate query or request is made to retrieve the RPKI validation state for a given prefix and ASN.Related Issues
N/A
Motivation and Context
Previously, RPKI validation was limited to Cloudflare’s API. This change adds flexibility by allowing users to select their preferred RPKI validation backend and specify custom server URLs. This is particularly useful for deployments that require integration with local Routinator instances or other RPKI validation services, improving adaptability and control over RPKI validation sources.
Tests
structured.pyare respected and that the correct backend and server URL are used for lookups.