Feature Overview

Implement a "resourceSelector" in ConfigurationPolicies, similar to its current "namespaceSelector", where the controller would fetch and iterate over the names returned from the resource selector for a particular object.

Goals

• (See overview)

Requirements

(Optional) Use Cases

• Simplifies the user experience, compared to the custom logic currently required with object-templates-raw, allowing filtering by name or by label
• Allows enforcing an object without a name specified.

Questions to answer

• How will the interplay with templating be affected for this?
• How would a ConfigurationPolicy with multiple object-templates be handled? It seems this would need to be implemented alongside each object-template.

Out of Scope

• ...

Background, and strategic fit

This Section: What does the person writing code, testing, documenting
need to know? What context can be provided to frame this feature?

Assumptions

• ...

Customer Considerations

• ...

Documentation Considerations

Questions to be addressed:

• What educational or reference material (docs) is required to support this
  product feature? For users/admins? Other functions (security officers, etc)?
• Does this feature have a doc impact?
• New Content, Updates to existing content, Release Note, or No Doc Impact
• If unsure and no Technical Writer is available, please contact Content
  Strategy.
• What concepts do customers need to understand to be successful in
  [action]?
• How do we expect customers will use the feature? For what purpose(s)?
• What reference material might a customer want/need to complete [action]?
• Is there source material that can be used as reference for the Technical
  Writer in writing the content? If yes, please link if available.
• What is the doc impact (New Content, Updates to existing content, or
  Release Note)?