Skip to content

Conversation

@JeffeyL
Copy link
Contributor

@JeffeyL JeffeyL commented Mar 26, 2024

When all ConfigurationPolicies have RemediationAction InformOnly, the root Policy is also set to have RemediationAction InformOnly. However, InformOnly is not valid on a Policy, and was thus modified to be set to inform in this case.

Ref: https://issues.redhat.com/browse/ACM-10534

@mprahl
Copy link
Member

mprahl commented Apr 2, 2024

/hold

}

// "InformOnly" should only apply to ConfigurationPolicies
if action == "InformOnly" {
Copy link
Member

@mprahl mprahl Apr 2, 2024

Choose a reason for hiding this comment

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

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.

/unhold

When all ConfigurationPolicies have RemediationAction InformOnly,
the root Policy is also set to have RemediationAction InformOnly.
However, InformOnly is not valid on a Policy, and was thus modified
to be set to inform in this case.

Signed-off-by: Jeffrey Luo <[email protected]>
@openshift-ci openshift-ci bot added the lgtm label Apr 3, 2024
@openshift-ci
Copy link

openshift-ci bot commented Apr 3, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JeffeyL, 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-ci openshift-ci bot added the approved label Apr 3, 2024
@mprahl
Copy link
Member

mprahl commented Apr 3, 2024

/cherry-pick release-2.10

@openshift-cherrypick-robot

@mprahl: once the present PR merges, I will cherry-pick it on top of release-2.10 in a new PR and assign it to you.

In response to this:

/cherry-pick release-2.10

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@mprahl
Copy link
Member

mprahl commented Apr 3, 2024

/cherry-pick release-2.9

@openshift-cherrypick-robot

@mprahl: once the present PR merges, I will cherry-pick it on top of release-2.9 in a new PR and assign it to you.

In response to this:

/cherry-pick release-2.9

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-cherrypick-robot

@mprahl: cannot checkout release-2.10: error checking out "release-2.10": exit status 1 error: pathspec 'release-2.10' did not match any file(s) known to git

In response to this:

/cherry-pick release-2.10

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

@openshift-cherrypick-robot

@mprahl: cannot checkout release-2.9: error checking out "release-2.9": exit status 1 error: pathspec 'release-2.9' did not match any file(s) known to git

In response to this:

/cherry-pick release-2.9

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

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.

3 participants