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

Exploration: use rego for defining rules #30

Open
vdemeester opened this issue Jan 19, 2024 · 0 comments
Open

Exploration: use rego for defining rules #30

vdemeester opened this issue Jan 19, 2024 · 0 comments
Labels
kind/feature Categorizes issue or PR as related to a new feature.

Comments

@vdemeester
Copy link
Member

As of today, "rules" in catlin are hardcoded in go code. Ideally, we should be able to extend / modify rules based independently of the code. One idea would be to use rego and possibly opa as a library to be able to define rules "dynamically".

  • Catlin would ship with a default set of rules (embedded)
  • A user could override or add new rules with a configuration (in the repository, or global)

See, for example, https://github.com/enterprise-contract/ec-policies/blob/main/policy/lib/bundles.rego

@vdemeester vdemeester added the kind/feature Categorizes issue or PR as related to a new feature. label Jan 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/feature Categorizes issue or PR as related to a new feature.
Projects
None yet
Development

No branches or pull requests

1 participant