Migrating config servers when Cloud/Ops Manager Automation is used

There is documentation for migrating config servers

http://docs.mongodb.org/manual/tutorial/migrate-config-servers-with-different-hostnames/
http://docs.mongodb.org/manual/tutorial/migrate-config-servers-with-same-hostname/

However, this existing documentation does not say what to do if Cloud/Ops Manager Automation is being used. there should be documentation which describes how to migrate config servers in the presence of automation, ie. automation-aware versions of those docs

One possible approach would be to unmanage the cluster, make change outside Cloud/Ops Manager, then re-import it as follows

1. Unmanage processes from Cloud Manager:
   https://docs.cloud.mongodb.com/tutorial/unmanage-deployment/#remove-a-process-from-management
2. Follow the instructions on how to manually change CNAME in a sharded cluster outside Cloud Manager:
   • To configure different CNAME
     • http://docs.mongodb.org/manual/tutorial/migrate-config-servers-with-different-hostnames/
   • To retain the same CNAME:
     • http://docs.mongodb.org/manual/tutorial/migrate-config-servers-with-same-hostname/
3. Finally, re-import existing MongoDB processes for Automation.
   https://docs.cloud.mongodb.com//tutorial/add-monitored-deployment-to-automation/