OCP/Telco Definition of Done
https://docs.google.com/document/d/1TP2Av7zHXz4_fmeX4q9HB0m9cqSZ4F6Jd4AiVoaF_2s/edit#heading=h.gaa58bzbvwde
Epic Template descriptions and documentation.
https://docs.google.com/document/d/14CUCEg6hQ_jpsFzJtWo29GfFVWmun2Uivrxq3_Fkgdg/edit
ACM-wide Product Requirements (Top-level Epics)
https://docs.google.com/document/d/1uIp6nS2QZ766UFuZBaC9USs8dW_I5wVdtYF9sUObYKg/edit

*<--- Cut-n-Paste the entire contents of this description into your new
Epic --->*

Epic Goal

See feature https://issues.redhat.com/browse/ACM-1683 

Why is this important?

The current behaviors of musthave and mustonlyhave can be confusing, and do not behave close enough to `kubectl apply` like some users might be expecting. 

Scenarios

Users should be able to update/replace some deeply-nested resource fields without worrying about many other fields being improperly "reset" or needing to resort to putting the entire resource state in a `mustonlyhave` policy.

Acceptance Criteria

...

Dependencies (internal and external)

1. ...

Previous Work (Optional):

1. https://github.com/open-cluster-management-io/enhancements/pull/131/files 
2. https://github.com/JustinKuli/ocm-enhancements/blob/more-policy-compliance-types/enhancements/sig-policy/130-policy-merge-compliancetypes/README.md 
3. https://gist.github.com/JustinKuli/bf9f97bb3916ac9b694f2e77bcecc5a0 

Open questions:

1. …

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub
  Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Doc issue opened with a completed template. Separate doc issue
  opened for any deprecation, removal, or any current known
  issue/troubleshooting removal from the doc, if applicable.
• Considerations were made for Extended Update Support (EUS)