Open SimonBaeumer opened 4 months ago
Hi @SimonBaeumer. 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 /ok-to-test
on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test
label.
I understand the commands that are listed here.
[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: SimonBaeumer Once this PR has been reviewed and has the lgtm label, please assign mrogers950 for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.
/ok-to-test
/hold for test
See #512
@SimonBaeumer: The following test failed, say /retest
to rerun all failed tests or /retest-required
to rerun all mandatory failed tests:
Test name | Commit | Details | Required | Rerun command |
---|---|---|---|---|
ci/prow/e2e-aws-serial | fec136efd4e56b24c5a84b025997788202bc8e7a | link | true | /test e2e-aws-serial |
Full PR test history. Your PR dashboard.
we have implmentation in https://github.com/ComplianceAsCode/compliance-operator/pull/591
This PR adds an enhancement to add a field
LastScannedTimestamp
to theCheckResult
CR.This enhancement is planned to be implemented by myself. This first iteration is to get consensus on the feature request and discuss possible implementations if necessary.