Hey @jonna
Thanks for posting your question- it is an interesting one! I have not come across Replicate standards for version control as it typically is up to the customer based on their environment.
You can take snapshots of your Replicate environment in two ways:
1. At a global level, you can export the entire repository any time there is a change or a task added. This will require some manual steps or scripting to produce a file called Replication_Definition.json which you can then commit.
a. Stop all running tasks
b. export Replicate repository (with server info):
Running command prompt as administrator:
Example:
C:\Program Files\Attunity\Replicate\bin> repctl -d "C:\Program Files\Attunity\Replicate\data" exportrepository include_server_settings=TRUE
output should look like this:
{
"message": "Export succeeded",
"file_path": "C:\\Program Files\\Attunity\\Replicate\\data\\imports\\Replication_Definition.json"
}
[exportrepository command] Succeeded
2. At the task level, you can use the following repctl command to download the task .json anytime a change is made. This option may be helpful if you want to commit/track at the task level.
C:\Program Files\Attunity\Replicate\bin>repctl exportrepository task=test_juli
command exportrepository response:
{
"message": "Export succeeded",
"file_path": "C:\\Program Files\\Attunity\\Replicate\\data\\imports\\test_juli.json"
}
[exportrepository command] Succeeded
Note: if you did revert to an older version of a task/Replication_Definition.json file you would most likely need to do a reload or a restart from timestamp to reproduce associated metadata or sqlite files to get the task up and running.
Further reference:
https://help.qlik.com/en-US/replicate/November2021/Content/Global_Common/Content/SharedEMReplicate/D...
https://community.qlik.com/t5/Knowledge/Repctl-Stop-Start-Task-using-REPCTL-command-line-interface/t...
https://hdfiles.jitbit.com/getfile/eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzM3BhdGgiOiIzMjQ0OC8yOTM5...
Best,
Kelly
