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

Revert "Fix the conditions history in compliancyDetails" #99

Merged
merged 1 commit into from
Jan 23, 2023
Merged

Revert "Fix the conditions history in compliancyDetails" #99

merged 1 commit into from
Jan 23, 2023

Commits on Jan 23, 2023

  1. Revert "Fix the conditions history in compliancyDetails" 

    This reverts commit 0234403 since
conditions aren't meant to contain a history. They are supposed to
contain just the current state. See:
https://github.com/kubernetes/community/blob/master/contributors/devel/sig-architecture/api-conventions.md#typical-status-properties

The ConfigurationPolicy status events combined all conditions and led to the wrong
status message being stored in the Policy.

Relates:
https://issues.redhat.com/browse/ACM-3040

Signed-off-by: mprahl <mprahl@users.noreply.github.com>
    @mprahl
    mprahl committed Jan 23, 2023
    Configuration menu
    Copy the full SHA
    ae535ec View commit details
    Browse the repository at this point in the history