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

Take into account hierarchy when dealing with rule types #3626

Merged
merged 1 commit into from
Jun 14, 2024

Commits on Jun 14, 2024

  1. Take into account hierarchy when dealing with rule types

    Rule types are usable by projects down the hierarchy, this allows
    someone in a child project to create a profile that uses rule types
    approved in a parent project. This is very handy since folks with
    permission to write profiles don't need to have permissions to write
    rule types, they can simply use some already approved and created.
    
    This also adds the constraint that rule type names are unique down the
    hierarchy. That is, a user cannot create a rule type name that overrides
    a rule type that exists in a parent project.
    
    Signed-off-by: Juan Antonio Osorio <ozz@stacklok.com>
    JAORMX committed Jun 14, 2024
    Configuration menu
    Copy the full SHA
    821f0e0 View commit details
    Browse the repository at this point in the history