When the am config upgrader tool is run against FRAAS am configs it corrupts the uid attribute of EmailTemplateNode config changing:
This affects both services/realm/root/emailtemplatenode/1.0/organizationconfig.json and services/realm/root/emailtemplatenode/1.0/organizationconfig/defaultconfig.json files.
This was seen when upgrading configs from am 7.0.0-7a2542d1eb0c92350a1ef6b36cf8feccea5ca348 to am 7.0.0-726a7b3ff28ae4425660c314fcfd306b0d57f1ee.
#. Obtain a directory of am config suitable for am 7.0.0-7a2542d1eb0c92350a1ef6b36cf8feccea5ca348 (such as the FRaaS express am config) - Note. config must be stored under a DN other than dc=openam,dc=forgerock,dc=org to see any impact
#. Run the am-config-upgrader against this directory of config
#. Observe changes to EmailTemplateNode configs
Manually adjust this field's value after running the am config upgrader - Note. this isn't really an option as we want to use the config upgrader as part of our upgrade automation.