Hi! I am trying to clone a source, only changing its name (need to preserve all its associated objects), through the sp-config calls. I export Source, I search/replace source name, and when importing, it only renames the same source.
My goal is to clone some jdbc source, that has about 15 instances, but they share all (indeed, I developed rule to work towards the source name to be generic, so the jdbcProvisionin rule has to be shared between all sources).
Try Using Get Source API call to fetch the source, Replace the Source Name and import using the Create Source API call. This way all the configurations including username and password will be cloned.
This is a common issue when exporting/importing sources via SP-config. You need to make sure that you delete the ID at the start of the “object” node:
Just blank it out like this:
"object":{"id":""
the id in the “objects” node can be left as is, as it is referencing the export. The import needs can’t reference your current source ID as it will only overwrite where ID matches the object to be imported.
Hi Sebastian, I will try this. I am not sure what happens for objects like correlation, which has its own id, I will test if I change correlation in 1 source changes for all.
Hi Sebastian, it worked partially. I had to remove all ids (except for the owner object). In this case is a jdbc connector. I have remover the ootb group entitlement from schema, and created a new one with other name than “group”, but when imported, the group entitlement type is created, so I had to delete it. Finally, passwords fields of operations where not imported, so I have to entered manually.
Besides these particular issues, it really saves too much time in comparison to re-create all manually.
You can now use configuration hub UI to safely and easily migrate configurations between tenants while using the object mapping feature to configure object name substitution and attribute value tokenization.
When migrating configurations between different tenants, config hub will know how to handle the ids of the objects from the source tenant and will match objects by name and not by id, so you will not have the problem that you had with the sp-config api, which matched and changed the original source based on id.
Hi Yael, thanks very much! This case in particular is for cloning the same connector N times in the same tenant (because client has several instances of application, only the name of the source changes, also connection parameters).
I will take a look at the hub and assist at the webinar, besides this particular topic it will be very usefull, because we will have to migrate these cloned sources (there are about 15) to the production tenant, and I think this will help us a lot!
