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

Break policy engine plugins out into separate repos #35

Open
chrisohaver opened this issue Dec 1, 2021 · 0 comments
Open

Break policy engine plugins out into separate repos #35

chrisohaver opened this issue Dec 1, 2021 · 0 comments

Comments

@chrisohaver
Copy link
Member

chrisohaver commented Dec 1, 2021

Currently all policy engine plugins (opa, themis) are in the same repo.

I think it makes better sense to break these out into their own repositories.
The main driver being that it would keep the go module mgmt separate between policy engines.
Since policy is already an external plugin, this does not add significantly more work to users of policy engines.

I'm proposing to ...

  • Break opa and themis out into separate repos.
  • Move the firewall plugin into the root of the policy repo.
  • Consider renaming the plugin "policy" or renaming the repo "firewall" so the repo and the plugin name match.

This is disruptive. The changes would impact current users of the firewall plugin, requiring updating paths in plugin.cfg.

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

No branches or pull requests

1 participant