You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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 ...
This is disruptive. The changes would impact current users of the firewall plugin, requiring updating paths in
plugin.cfg
.The text was updated successfully, but these errors were encountered: