Value Statement

The ConfigurationPolicy has a namespaceSelector and, in the future, a resourceSelector, both of which allow an iteration over a list of objects. For flexibility, it would be ideal to have a context variable that users can use in the managed cluster Go templates to refer to the current namespace or object from the respective selector during each iteration.

Definition of Done for Engineering Story Owner (Checklist)

• The config-policy-controller is refactored to allow a template variable to be implemented for the current namespace from the namespaceSelector, without breaking current Go template flows, processing the templates only once (since a second processing could be unexpected for users that want to preserve the templates to pass them on to another process)
• Once resourceSelector is implemented, a template variable is implemented for the current resource from the resourceSelector

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.