Value Statement

As an ACM Policy user, I would like all policy template types to be supported with progressive policy rollout so that I can have a reliable rolloutStatus and can progressively enforce Gatekeeper constraints (i.e. audit -> audit + deny).

Definition of Done for Engineering Story Owner (Checklist)

• All policy controllers set the "policy.open-cluster-management.io/last-evaluated-generation" annotation to the policy status update event.
• The Status Sync controller honors that when setting the rolloutStatus

Development Complete

• The code is complete.
• Functionality is working.
• Any required downstream Docker file changes are made.

Tests Automated

• [ ] Unit/function tests have been automated and incorporated into the
  build.
• [ ] 100% automated unit/function test coverage for new or changed APIs.

Secure Design

• [ ] Security has been assessed and incorporated into your threat model.

Multidisciplinary Teams Readiness

• [ ] Create an informative documentation issue using the [Customer
  Portal_doc_issue template](
  https://github.com/stolostron/backlog/issues/new?assignees=&labels=squad%3Adoc&template=doc_issue.md&title=),
  and ensure doc acceptance criteria is met. Link the development issue to
  the doc issue.
• [ ] Provide input to the QE team, and ensure QE acceptance criteria
  (established between story owner and QE focal) are met.

Support Readiness

• [ ] The must-gather script has been updated.