This is related to slack discussions

https://redhat-internal.slack.com/archives/C0282HW2YHZ/p1764769854154099

https://redhat-internal.slack.com/archives/C0282HW2YHZ/p1764325987099969

For the following feature, documented here

https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.14/html-single/clusters/index#custom-auto-import-strat

https://docs.google.com/document/d/16XgHD5AjiTYsVBaOL5bATzQ0BXEX-NNatJxGQo00dWM/edit?usp=sharing

https://issues.redhat.com/browse/ACM-17217

The issue reported here:

1. The documentation doesn't explain why the 2 options are available and when to use one or the other ( what happens if one option is used ) . We need the docs to update this info
2. We just found out that this feature works differently if you create a new 2.14 hub vs upgrade to 2.14.  This to me looks like an issue; it is also not documented that it works this way
   This is what the QE team is looking at right now
   Looks like the server foundation team is creating the configMap and sets the option to ImportAndSync when a hub is upgraded to 2.14, probably to keep the same user experience as you move to the new version.
   But this cancels the new enhancement if you come from an ACM upgrade path, as probably most of our users do.