Description of problem:

if you then manually modify the project request template on the cluster, when the policy reconciles it mixes all the objects and it duplicates different values or some changes are not propagated.

Version-Release number of selected component (if applicable):

How reproducible:

always

Steps to Reproduce:

1.  create policy template
2.  try to update it.
3. ...

Actual results:

weird merging 

Expected results:

Additional info:

First of all, it seems that the engineering team has got the same weird behavior we noticed (strange merges, and not reacting controller if you change the template on the managed cluster).
But, maybe we managed to define a better WA, it seems that if you use the application management component of RHACM, enforcing the template as if it was an application manifest by the use of a RHACM subscription (with apps.open-cluster-management.io/reconcile-option: replace), the behavior is correct, indeed, if you try to change the template on the managed cluster, ACM does enforce the right template within seconds, and even if the template is already present, RHACM enforces the app manifest as expected, without any strange merge, using a replace strategy.
We believe that this one is an important information for the engineering team, because if the application controller can enforce the template in the right way as we experimented, it means that a bug inside governance policy controller should be present, when it comes the management of "mustonlyhave" compliance type.