Move rego utilities to some kind of "stackable library of rules"

Open
#494 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
kubernetes, rust
Domain
authorization, devops

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.

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

Dominant language
Rust
Stars
21
Forks
5
Avg merge
12h 44m
Merged PRs (30d)
11

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from stackabletech/opa-operator

All issues in stackabletech/opa-operator

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.