Value Statement

As a policy user, I want to know why my configuration policy is noncompliant when I think it should be compliant.

Definition of Done for Engineering Story Owner (Checklist)

• Add an optional field of `spec.object-templates[*].recordDiff`that has the options of `Log` and `None`. It would default to the `None` behavior when not specified.
• When a configuration policy object template is not compliant, even if it will be updated with enforce, a diff in YAML format should be shown in the logs (similar format to the `diff` CLI tool) when recordDiff is set to `Log`.

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.