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
Expose router in plugin manager #4020
Conversation
d7ab19e
to
724e6d5
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this PR and sorry for the slightly delayed response!
I don't have a problem with exposing the router on the manager but I'd like to see some small tweaks to the PR. Let me know if you think the ones I outlined below will work!
No worries. I will check this out next week as I am currently away for the holiday |
@tsandall, I have made the suggested updates. Please re-review. Thanks! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for contributing this 👏 🎉
Would you mind squashing those commits, and checking that the message roughly fits in with the guides here? https://www.openpolicyagent.org/docs/latest/contributing/#commit-messages Thank you! |
In order to expose the http router to plugins a private router property was added to the plugin manager along with a GetRouter method to access it. A router is also initialized in the NewRuntime function if one is not provided in the runtime params. Fixes open-policy-agent#2777 Signed-off-by: Branden Horiuchi <Branden.Horiuchi@blackline.com>
@srenatus commits squashed and message updated. |
Addresses #2777 by