EOPA and OPA #714
-
Hi Now that https://github.com/open-policy-agent/eopa has been added to the public repo, will opa and eopa be merged or will they be treated as separate apps? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
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. |
Beta Was this translation helpful? Give feedback.
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.