Skip to content
Discussion options

You must be logged in to vote

Hello! 👋

So, without any concrete promises, let me try to fill in some blanks: OPA has always tried to be a lean, simple application and Go module. EOPA is the opposite of that, it's carrying loads of dependencies to satisfy specific, data-heavy requirements. There's a place for both of them.

Some things you find today in EOPA will find their way into OPA; some things may become separate Go modules so you can pick-and-choose in your own spin of "OPA++". EOPA currently serves as an OPA distribution that bundles all the plugins for data-heavy use cases in one build/binary. OPA is not going to disappear.

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by naeem
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
2 participants