Value Statement

When a user has a policy with complicated templates, which may pull information from many objects on the cluster, it can be difficult to fully know what "dependencies" the policy has. The template-resolver CLI can connect to a live cluster and execute the templates, but a user is not as easily able to test what would happen if some of those resources change. The dryrun CLI could be used to test those kinds of changes, but requires the full YAML for the objects it uses.

The template-resolver should be able to output the full YAML of objects it uses in lookups, so that they can easily be modified by users for tests utilizing dryrun.

Definition of Done for Engineering Story Owner (Checklist)

• [ ] template-resolver provides some way to get all the YAML of all the resources it used while resolving templates
• [ ] that YAML will work as an input to dryrun

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 template that you can access from [The Playbook](

https://docs.google.com/document/d/1YTqpZRH54Bnn4WJ2nZmjaCoiRtqmrc2w6DdQxe_yLZ8/edit#heading=h.9fvyr2rdriby),

and ensure doc acceptance criteria is met.

• Call out this sentence as it's own action:

• [ ] Link the development issue to the doc issue.

Support Readiness

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