Feature Goal

ACM 2.12 added support for discovering policies on managed clusters.  These policies are identified using search and do not have to be distributed with the Policy framework, but could have been created by other mechanisms.  For any discovered policies that can alert on Compliance/NonCompliance there needs to be a way to track the history of policy.  Each policy enforcement point may have a unique way to track history or may not.  History could be provided leveraging the ACM Policy framework by identifying policy events and sending them to the policy compliance history API.

Why is this important?

Solve the lack of violation history for policies that are discovered and fill a feature gap between policy-framework deployment and standalone deployment patterns

Scenarios

https://docs.google.com/document/d/10dMHO-vIQ80j4BXx4r-8lhDjGWoQ0qb985aTlindK0M/edit?disco=AAABXdIYo2o 

Acceptance Criteria

• ConfigurationPolicy, CertificatePolicy, OperatorPolicy
  • Append the last 10 violation status events for the policy to the status; similar to existing behavior with Policy kind deployment
• Update "Policy deployment comparison table" doc
  • Feature:  Compliance history
  • Deployed with external tools
    • Change something similar to Policy framework column; e.g. "You can view the last 10 events..."
• UI work:
  • Move the existing history page
    • The entire history page should be moved into the Policy details page, as a new tab; either "History" or "Event history"
      • This will consolidate the user experience around "details" of the policy and allow for the existing Policy kind UX and the Discovered policies UX to be consistent
    • The original "View history" link in the Policy details > Results page should link to the new tab in the policy details page

Dependencies (internal and external)

Previous Work (Optional):

1. ...

Open questions:

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Doc issue opened with a completed template. Separate doc issue
  opened for any deprecation, removal, or any current known
  issue/troubleshooting removal from the doc, if applicable.