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

Pulsar event listener #6747

Closed
dgreene1 opened this issue May 14, 2024 · 3 comments
Closed

Pulsar event listener #6747

dgreene1 opened this issue May 14, 2024 · 3 comments

Comments

@dgreene1
Copy link

What is the underlying problem you're trying to solve?

We want to have OPA be up to date with the newest event in a Pulsar topic.

Describe the ideal solution

The same as https://docs.styra.com/enterprise-opa/tutorials/using-data/streaming-kafka but for Pulsar.

Describe a "Good Enough" solution

A generic endpoint for pushing data. I believe this already exists. The problem here is that how does the central “pusher” know of all of the OPA instances? How does it know that they all accepted the push?

Additional Context

@srenatus
Copy link
Contributor

Thanks for the request!

A generic endpoint for pushing data. I believe this already exists. The problem here is that how does the central “pusher” know of all of the OPA instances? How does it know that they all accepted the push?

For completeness' sake, there's the Data API which lets you PUT data updates into OPA. But you're correct, a central pusher service -- which is outside of the scope of OPA -- would need to know all OPA instances that it would push data to. Alternatively, it could distribute bundles (or delta bundles) and the OPA instances would fetch them and keep themselves updated (periodically, or via long polling).

Since OPA itself has no data plugins like EOPA, I don't know if this feature request has much chances. It would require quite a bit of effort to bring dynamic data plugins to OPA. It's more feasible as a feature request to EOPA, but I'm afraid we don't track them here (but it's been noted now 📝).

@ashutosh-narkar
Copy link
Member

Closing this for now as it seems outside the scope of OPA. Feel free to re-open if anything OPA-specific would be needed. Thanks.

@ashutosh-narkar ashutosh-narkar closed this as not planned Won't fix, can't repro, duplicate, stale May 14, 2024
@dgreene1
Copy link
Author

No problem. I will either enhance permit’s OPAL, wait for Enterprise OPA to implement it, or go elsewhere entirely.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants