Uploaded image for project: 'Cloud Infrastructure Security & Compliance'
  1. Cloud Infrastructure Security & Compliance
  2. CMP-2614

Implement update timestamps on ComplianceCheckResults

XMLWordPrintable

    • Icon: Story Story
    • Resolution: Done
    • Icon: Blocker Blocker
    • compliance-operator-1.6.0
    • None
    • None
    • None
    • BU Product Work
    • 2
    • False
    • None
    • False
    • CMP-2632 - Need timeStamp on CCR for scheduled scan
    • CMP Sprint 86, CMP Sprint 87, CMP Sprint 88

      Currently, the ComplianceCheckResult object has a creation timestamp, but not an updatedAt timestamp. This makes it difficult to know when the last time a ComplianceCheckResult was updated, unless you assume all results are the latest and know to fetch the latest state from the parent scan.

      We can make this easier for users by updating the ComplianceCheckResult to include an updatedAt timestamp or even using the status condition that are already present in other compliance operator resources.

      This is necessary for ACS to consume compliance data from the compliance operator because it forces the CRD to update, which sensor will pickup and forward along to central.

          There are no Sub-Tasks for this issue.

              wenshen@redhat.com Vincent Shen
              lbragsta@redhat.com Lance Bragstad
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: