Run an Update Set Once Clone Completes

[jmiskey]

We have a situation where we have scheduled a weekly clone from our PROD environment to a special DEV2 environment that was set up for us.  We have created some Custom Themes that we would like transferred to this DEV2 environment.  We tried setting "Preservers", in hopes that the Clone would not overwrite these Custom Themes, but it did not work (and research into old Community questions seems to suggest that this may not work quite as expected).

So we have a different approach that we would like to try.  We want to create an Update Set that we import, but do not Post/Commit, in our PROD environment.  Then, the Clone should copy that uncommitted Update Set to the DEV2 environment.  We would like to then run this Update Set once our Clone is completed.  So we have a few questions regarding the best way of doing this, including:

- What is the best way of running this Update Set once the clone is complete? 

- Would you do that with a Scheduled Job, or in some other manner?

- Can a Scheduled Job actually run/commit an update set?

- If it can be done with a Scheduled Job, is it possible to make it wait until the Clone is complete, or do I just need to pick a time to run it when I know that the Clone should be complete (in a perfect scenario, it will run automatically upon completion of the clone)?

Thanks

[Kirby R]

HI @jmiskey ,

What version are your instances? We've been cloning few times already(San Diego) and there's no issue with themes. 

Can you possibly share your preservers for themes?

[jmiskey]

They are both Tokyo instances.  Here is the preserver we set up:

We then set-up a profile that uses that new preserver:

and then run our clones using that profile.

[Kirby R]

Hi @jmiskey ,

Can you take a look at your update set and its customer updates? Those customer updates should contain the table name the themes you want to preserve. Now you can add those in the preserver including the polaris property from above. 

[jmiskey]

This is what the update set records look like:

So based on this, I am not sure how to incorporate your suggestion.

And ideas?

[Kirby R · Accepted solution]

Customer Update name is basically <table_name>_<sys_id of the record in that table>. So what you need to do is add these tables in your preservers similar to what you have done for sys_properties.

Example:

sys_ux_style, m2m_theme_style

You can do more granular and include the sys_id in the filter in your preserver