Skip to content

[enterprise-4.19] :oc events command needs to be updated #89384

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

Merged
merged 1 commit into from
Feb 28, 2025
Merged

[enterprise-4.19] :oc events command needs to be updated #89384

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions modules/compliance-crd-advanced-compliance-scan.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@ The Compliance Operator includes options for advanced users for debugging or int
apiVersion: compliance.openshift.io/v1alpha1
kind: ComplianceScan
metadata:
name: <name of the scan>
name: <name_of_the_compliance_scan>
spec:
scanType: Node <1>
profile: xccdf_org.ssgproject.content_profile_moderate <2>
Expand Down Expand Up @@ -55,5 +55,5 @@ You can programmatically fetch the `ComplianceScans` events. To generate events

[source,terminal]
----
oc get events --field-selector involvedObject.kind=ComplianceScan,involvedObject.name=<name of the suite>
oc get events --field-selector involvedObject.kind=ComplianceScan,involvedObject.name=<name_of_the_compliance_scan>
----
2 changes: 1 addition & 1 deletion modules/compliance-crd-compliance-suite.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@ For `Node` type scans, you should map the scan to the `MachineConfigPool`, since
apiVersion: compliance.openshift.io/v1alpha1
kind: ComplianceSuite
metadata:
name: <name of the scan>
name: <name_of_the_suite>
spec:
autoApplyRemediations: false <1>
schedule: "0 1 * * *" <2>
Expand Down