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

Separate Category and Capability Validation #304

Commits on Nov 2, 2023

  1. Separate Category and Capability Validation

    This commit removes the default set of category and capability validation
    as a part of the operatorhubio validator.
    
    As we have a mechanism for custom category validation, and there is
    significantly more churn on that specific validation, this commit
    separates the default operatorhubio validator from a distinct default
    categories validator. This allows users that want to continue to use the
    default set of categories to still do so, and if there are custom
    categories they would like to include they are free to use the dynamic
    categories validation option instead.
    
    This commit also does the same separation for capability validation.
    There is no implementation of custom capability validation (as there is
    less churn and no explicit need for that yet) -- adding custom
    capability validation should be trivial in a future commit.
    
    This commit accomplishes this by deprecating the existing validator and
    creating a v2 version of the operatorhubio validator.
    
    Additionally, this commit adds 'Observability' to the category list.
    kevinrizza committed Nov 2, 2023
    Configuration menu
    Copy the full SHA
    e2aeec7 View commit details
    Browse the repository at this point in the history