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.

Sign up for GitHub

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

Jump to bottom

OperatorPolicy Templates #235

Merged
merged 7 commits into from
May 2, 2024
Merged

OperatorPolicy Templates #235

merged 7 commits into from
May 2, 2024

Commits on May 1, 2024

  1. Remove hub-template error handling 

    The framework-addon now handles emitting compliance events for those
errors for all template policy types.

Refs:
 - https://issues.redhat.com/browse/ACM-10858

Signed-off-by: Justin Kulikauskas <jkulikau@redhat.com>
    @JustinKuli
    JustinKuli committed May 1, 2024
    Configuration menu
    Copy the full SHA
    06bdc09 View commit details
    Browse the repository at this point in the history

  2. Support templates in OperatorPolicy 

    The Subscription and OperatorGroup fields can now utilize templates. The
resolver uses the DynamicWatcher already used by the controller, so no
additional plumbing was needed for new watches or in order to share a
cache.

Refs:
 - https://issues.redhat.com/browse/ACM-10858

Signed-off-by: Justin Kulikauskas <jkulikau@redhat.com>
    @JustinKuli
    JustinKuli committed May 1, 2024
    Configuration menu
    Copy the full SHA
    c269455 View commit details
    Browse the repository at this point in the history

  3. Update dependency-watches library for DeepCopy 

    The library now does the DeepCopy for us, to prevent accidental
mutations to objects in the cache.

Signed-off-by: Justin Kulikauskas <jkulikau@redhat.com>
    @JustinKuli
    JustinKuli committed May 1, 2024
    Configuration menu
    Copy the full SHA
    36689fc View commit details
    Browse the repository at this point in the history

  4. Use a newer quay version for operatorpolicy tests 

    From some test runs, it seems like some of the 3.8.x releases do not
always have the quayecosystems CRD, which makes the tests inconsistent.
From what I can tell, *none* of the 3.10.x releases will have that CRD,
so it should be consistent.

Signed-off-by: Justin Kulikauskas <jkulikau@redhat.com>
    @JustinKuli
    JustinKuli committed May 1, 2024
    Configuration menu
    Copy the full SHA
    bad4d20 View commit details
    Browse the repository at this point in the history

  5. Wait for actual ConstraintsNotSatisfiable reason 

    This test started failing relatively often. Debugging revealed that the
Subscription was getting into a ResolutionFailed=True condition, but
that it did not have the expected ConstraintsNotSatisfiable reason; it
looked like it was failing to resolve because the connection was refused
to the catalog.

Refs:
 - https://issues.redhat.com/browse/ACM-11414

Signed-off-by: Justin Kulikauskas <jkulikau@redhat.com>
    @JustinKuli
    JustinKuli committed May 1, 2024
    Configuration menu
    Copy the full SHA
    4f306c4 View commit details
    Browse the repository at this point in the history

  6. Add checkCompliance function for debugging tests 

    The full policy status is often helpful when understanding what might be
unexpectedly happening in some of the operatorpolicy tests.

Signed-off-by: Justin Kulikauskas <jkulikau@redhat.com>
    @JustinKuli
    JustinKuli committed May 1, 2024
    Configuration menu
    Copy the full SHA
    0b74448 View commit details
    Browse the repository at this point in the history

  7. More version fixes for tests 

    This should help with some consistency.

Signed-off-by: Justin Kulikauskas <jkulikau@redhat.com>
    @JustinKuli
    JustinKuli committed May 1, 2024
    Configuration menu
    Copy the full SHA
    3b6ef6a View commit details
    Browse the repository at this point in the history