Epic Goal

As ACM-5892 solution is difficult to fully complete we work on a solution which gives quick help e.g. by logging the diff of a Policy violation

Long term we want to include a Diff-feature in our compliance history

it was discussed that customers expect help to find out why a Policy is not compliant,
we are flexible how to achieve this. Another solution e.g. could be a dry-run feature....

*Why is it important?

• Policy users/developers give us the feedback that it's sometimes hard to see why a policy is not compliant, hence they
  worry to set a Policy to enforce

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.