CtrlK
BlogDocsLog inGet started
Tessl Logo

nicholasjackson/opa-rego-language

Rego is the declarative policy language used by Open Policy Agent (OPA). This tile covers writing and testing Rego policies for Kubernetes admission control, Terraform and infrastructure-as-code plan validation, Docker container authorization, HTTP API authorization, RBAC and role-based access control, data filtering, metadata annotations with opa inspect, and OPA policy testing with opa test.

99

1.19x

Quality

Pending

Does it follow best practices?

Impact

99%

1.19x

Average score across 31 eval scenarios

SecuritybySnyk

Pending

The risk profile of this skill

Overview
Eval results
Files

task.mdevals/scenario-1/

Access Control: Common Testing Pattern

Write a Rego policy that denies access when the requesting user does not have the required role for the action.

Also write a _test.rego file that tests the policy. The test file must be named with the _test.rego suffix, use the _test package suffix, prefix all test functions with test_, mock input using with input as, and include both a passing case (user has the required role) and a failing case (user does not have the required role).

Input

{
  "user": "alice",
  "action": "delete",
  "roles": ["viewer"]
}

Data

data.role_permissions maps roles to permitted actions:

{
  "admin": ["read", "write", "delete"],
  "editor": ["read", "write"],
  "viewer": ["read"]
}

Expected behaviour

  • allow is true when the user has a role that permits the requested action
  • allow is false otherwise
  • Alice (viewer) is denied delete
  • A user with admin role is allowed delete

README.md

rules.md

tile.json