Skip to content

five-c: Create rules-based engine #409

Closed

Description

@pombredanne

Create basic rules-based engine using the designed policy approach.
Deploy for test usage

Activity

  1. self-assigned this
    on Jul 6, 2026
  2. moved this to In progress in 00-AboutCodePlanneron Jul 6, 2026
  3. tdruez commented on Jul 21, 2026

    @tdruez
    Contributor

    Rules-based engine implemented in:

    Policy Rules Engine

    • Rules engine that evaluates configurable compliance rules against products and records violations
    • Five built-in rules covering usage policy errors/warnings, license policy errors/warnings, and license coverage gaps
    • Per-dataspace configuration to enable/disable rules and override thresholds
    • Automatic re-evaluation triggered when a product, its packages, or the dataspace configuration changes
    • Background task support for evaluating one product or all products at once
    • Webhook notifications on new violations detected or violations resolved
    • Manual re-evaluation action available from the product admin and the compliance tab
    • Compliance dashboard updated with a policy violations metric card and table column
    • Per-product compliance tab showing active violations with rule details and detection date
    • Product list filter to show only products with (or without) active policy violations
    • REST API endpoint exposing active policy violations per product

    Usage

    1. Configure rules for a Dataspace

    Open the Dataspace admin and expand the Policy Rules Configuration section.
    Each rule can be individually enabled or disabled. An optional threshold lets you set the minimum number of violations required to trigger a rule, if left blank, the rule's default threshold applies.

    Screenshot 2026-07-21 at 14 44 48

    2. Evaluation

    Once rules are enabled, all products in the dataspace are evaluated automatically whenever a product is saved, a package is added or removed, or the dataspace configuration changes. Evaluation can also be triggered manually from the product list (admin action) or from the product compliance tab (re-evaluate button).

    Screenshot 2026-07-21 at 14 46 31

    3. Reviewing violations

    Active violations appear in two places:

    • The compliance dashboard shows a policy violations count per product and a global metric card summarizing affected products across the dataspace.
      Screenshot 2026-07-21 at 14 45 50

    • The product compliance tab lists each triggered rule with its description, the number of violating objects, and the detection date. Each entry links directly to the filtered inventory view so the issue can be addressed immediately.
      Screenshot 2026-07-21 at 14 46 24

    Screenshot 2026-07-21 at 14 46 18

    4. Notifications

    Webhook notifications can be configured in the Dataspace admin under the Notifications section. Two event types are available:

    • policy.violation_detected fires when new violations are found during an evaluation run.
    • policy.violation_resolved fires when previously open violations are resolved, either because the underlying issue was fixed or because the rule was disabled.
    Screenshot 2026-07-21 at 14 47 14
  4. pombredanne commented on Jul 21, 2026

    @pombredanne
    MemberAuthor

    Thanks!

  5. moved this from Done to Reviewed in 00-AboutCodePlanneron Jul 21, 2026
  6. moved this from Reviewed to Done in 00-AboutCodePlanneron Aug 3, 2026
  7. moved this from Done to Reviewed in 00-AboutCodePlanneron Aug 4, 2026
  8. moved this from Reviewed to Validated in 00-AboutCodePlanneron Aug 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions