We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
In order to avoid conflicts it would be great to specify the source database, analog to bgpq3 -S <source>.
bgpq3 -S <source>
I'm happy to contribute some code but would like to discuss general design in advance.
The biggest question I'd like to discuss is in which way this should be passed via the API, some suggestions:
/<string:format>/<string:obj>/<string:policy>?source=<string> /<string:source>/<string:format>/<string:obj>/<string:policy>
The text was updated successfully, but these errors were encountered:
Agreed. There are a bunch of reasons one might want this. For us, one use case is for lists that should use only "properly authenticated" sources.
I'm happy to contribute some code but would like to discuss general design in advance. The biggest question I'd like to discuss is in which way this should be passed via the API, some suggestions: /<string:format>/<string:obj>/<string:policy>?source=<string> /<string:source>/<string:format>/<string:obj>/<string:policy>
I think there is a place for both forms:
<string:source-list-name>
The use case you've described would probably require the first style. Ours would use the second.
Thoughts?
Sorry, something went wrong.
Oh, and I think that if both named-list and parameter list were provided, the expected result would use the intersection of the two sets. Right?
No branches or pull requests
In order to avoid conflicts it would be great to specify the source database, analog to
bgpq3 -S <source>
.I'm happy to contribute some code but would like to discuss general design in advance.
The biggest question I'd like to discuss is in which way this should be passed via the API, some suggestions:
The text was updated successfully, but these errors were encountered: