Feature Overview

Support the mutating policy features in Gatekeeper in the Discovered policies UI

Goals

This Section: Provide high-level goal statement, providing user context
and expected user outcome(s) for this feature

• More broadly support and provide a UX for Gatekeeper in RHACM:  https://open-policy-agent.github.io/gatekeeper/website/docs/mutation 

Requirements

This Section: A list of specific needs or objectives that a Feature must
deliver to satisfy the Feature.. Some requirements will be flagged as MVP.
If an MVP gets shifted, the feature shifts. If a non MVP requirement slips,
it does not shift the feature.

(Optional) Use Cases

This Section:

• Display the Gatekeeper Mutation CRDs in the Discovered policies experience
  • AssignMetadata - defines changes to the metadata section of a resource
  • Assign - any change outside the metadata section
  • ModifySet - adds or removes entries from a list, such as the arguments to a container
  • AssignImage - defines changes to the components of an image string

Questions to answer

• Is it possible to have a related resources experience for mutations, does it make sense?
  • How would we know that the resource, was in fact, mutated by the Mutation policy?
    • Need to investigate if there is anything on the resource that indicates it was modified by GK
    • If events are the only metadata available, we will not do a related resources experience completely.

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)?