-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Flag to fail OPA runtime if some of the bundle was not found #6713
Comments
How are you deploying OPA? For example, if you use Kubernetes you can configure a
OPA can be loaded with one or more bundles. So to panic if one of them fails activation does not seem appropriate. The client can use the Health API or Status API for example to get more info and behave accordingly. |
It might work, but I also noticed |
That's probably something that can be improved. |
This issue has been automatically marked as inactive because it has not had any activity in the last 30 days. Although currently inactive, the issue could still be considered and actively worked on in the future. More details about the use-case this issue attempts to address, the value provided by completing it or possible solutions to resolve it would help to prioritize the issue. |
What is the underlying problem you're trying to solve?
In our use case, it's very crucial to load all bundles on OPA startup. Whenever error happens, we need to handle it the way we want, and not just see it in logs.
Describe the ideal solution
In OPA runtime golang lib, when we start a server, I want to panic, if some of my bundles fail to load.
Now I see error log like this:
But I want lib to panic, so I could catch this panic and write my logic of how to handle this error.
Describe a "Good Enough" solution
Panic if bundle load fails for whatever reason.
The text was updated successfully, but these errors were encountered: