Value Statement

As a Policy Generator user, I'd like to generate policies which utilize the new native Gatekeeper constraint support in ACM so that I can just deploy my existing Gatekeeper constraints using ACM policies.

Definition of Done for Engineering Story Owner (Checklist)

• Create a new Policy Generator release branch since this will include a change in default behavior.
• The Policy Generator's informGatekeeperPolicies field should default to false (currently true).
• When informGatekeeperPolicies is set to false, treat input manifests that are Gatekeeper ConstraintTemplates and constraints as we do for policy manifests (e.g. a ConfigurationPolicy or CertificatePolicy). In other words, directly insert them in the generated policy's "policy-templates" array.

Development Complete

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

Tests Automated

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

Secure Design

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

Multidisciplinary Teams Readiness

• [x] 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.
• [x] Provide input to the QE team, and ensure QE acceptance criteria
  (established between story owner and QE focal) are met.

Support Readiness

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