stackabletech / stackabletech/opa-operator
Move rego utilities to some kind of "stackable library of rules"
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 21
- Forks
- 5
- Avg merge
- 12h 44m
- Merged PRs (30d)
- 11
Description
This should ideally be moved to some kind of "stackable library of rules", but we don't currently have a good way to deploy and manage that.
Originally posted by @nightkr in https://github.com/stackabletech/opa-operator/pull/433#discussion_r1371502535
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating the current Rego utilities and how the operator deploys and manages OPA rules, then review the discussion in pull request 433. Done means an agreed, implementable design for a stackable rule library and its deployment and management path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, rust
- Domain
- authorization, devops
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100