CMP-3730: Updated banner_etc_issue to use variable - #14615
Conversation
|
Hi @vickeybrown. Thanks for your PR. I'm waiting for a ComplianceAsCode member to verify that this patch is reasonable to test. If it is, they should reply with Regular contributors should join the org to skip this step. Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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-sigs/prow repository. |
|
/ok-to-test |
|
/retest-required |
|
/ok-to-test |
|
/retest |
709a72d to
813621b
Compare
|
/ok-to-test |
|
/test e2e-aws-openshift-node-compliance |
813621b to
b9ca2bb
Compare
d961570 to
3d58b59
Compare
04ded2e to
1604669
Compare
1604669 to
d9c2a14
Compare
yuumasato
left a comment
There was a problem hiding this comment.
Looks good, just a minor clean up on legacy remediation metadata.
| @@ -5,16 +5,15 @@ kind: MachineConfig | |||
| metadata: | |||
| labels: | |||
| machineconfiguration.openshift.io/role: master | |||
There was a problem hiding this comment.
@vickeybrown Please, remove the whole metadata block, it is not necessary and the role can be misleading, since the remediation applies on both master and worker.
CO will infer the role based on the pools it is scanning and remediating, and the MC name is inferred from the rule name
See these for example:
content/shared/macros/10-kubernetes.jinja
Line 638 in d7ad56f
fixed linting issues
d9c2a14 to
3769e9d
Compare
|
@vickeybrown: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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-sigs/prow repository. I understand the commands that are listed here. |
Taimur's changes have been addressed.
Description:
banner_etc_issue currently uses a hardcoded remediation value, while the check allows for the configuration of different values via variable. This update changes it to follow that flow to allow for successful remediations.
This won't work without also having the changes in ComplianceAsCode/compliance-operator#1198