Value Statement

As an ACM policy developer and user, the compliance history API needs to be exposed for users to query it and for managed clusters to record compliance events in it.

Definition of Done for Engineering Story Owner (Checklist)

• The HTTP endpoint will be exposed using an Ingress object. On OpenShift clusters, special annotations will create a route for it that is protected by TLS. On other Kubernetes distributions, a certificate must be provided for the Ingress object.

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.