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

Handle policy dependencies of Gatekeeper types #105

Conversation

JustinKuli
Copy link
Member

Originally, policy dependencies could only handle objects that had a status.complianceState field. Gatekeeper ConstraintTemplates and Constraints do not have this field, but we assign them a compliance in a similar way elsewhere. This commit allows these Gatekeeper types to be used for policy dependencies like a user might expect.

Refs:

Originally, policy dependencies could only handle objects that had a
`status.complianceState` field. Gatekeeper ConstraintTemplates and
Constraints do not have this field, but we assign them a compliance in
a similar way elsewhere. This commit allows these Gatekeeper types to
be used for policy dependencies like a user might expect.

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

Signed-off-by: Justin Kulikauskas <[email protected]>
Copy link
Member

@mprahl mprahl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A couple of minor comments but afterwards, I'll approve it. This looks great!

Since there are more cases now(for the Gatekeeper types) it became clear
that diagnosing why a policy dependency was not met might be difficult.
This adds reasons to the unmet dependencies which will be logged, and
which might in the future be used in status messages.

Signed-off-by: Justin Kulikauskas <[email protected]>
Copy link

openshift-ci bot commented Jan 10, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JustinKuli, mprahl

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-bot openshift-merge-bot bot merged commit efe129c into open-cluster-management-io:main Jan 10, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants