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

Improve OperatorGroup removal logic #230

Commits on Apr 23, 2024

  1. Improve OperatorGroup removal logic

    In some clusters, a default OperatorGroup might be provided in a
    namespace for "global" operators. This OperatorGroup was not being
    correctly identified by the policy: in fact any pre-existing group that
    did not match the group specified by the policy, or the one that would
    be generated when the policy does not specify a group, was not reported
    correctly.
    
    Now, pre-existing "special" operator groups should be reported and
    handled correctly. If they are owned by another resource, they will be
    considered as "used" for the purposes of the DeleteIfUnused setting.
    
    This also removes the "regular" `Delete` option for OperatorGroups: that
    was too likely to cause confusion.
    
    Refs:
     - https://issues.redhat.com/browse/ACM-11022
     - https://issues.redhat.com/browse/ACM-11077
    
    Signed-off-by: Justin Kulikauskas <jkulikau@redhat.com>
    JustinKuli committed Apr 23, 2024
    Configuration menu
    Copy the full SHA
    06ba1e1 View commit details
    Browse the repository at this point in the history