Import and Export of Qlik replicate tasks using IaC Technology (Terraform)

[Rak]

We are using qlik replicate to replicate the data from sql server to kafka and gcs targets. 

Currently we using the Import API's for replicate tasks to import the tasks into replicate server and we are using jinja templates to create the task json by passing the configuration and tablenames (List of table is not static and passed at the time of json creation) and import those json programmatically (Jenkins) and as we are creating the json task on the fly using templates, we are missing the traceability, which is really a challenging as changes are not being recorded. 

Ask here is, How can we make it more configurable manner with traceability / recoverability for each qlik task. Curious to know if someone has already done this using terraform. 

Can this be achieved using Terraform? or any other IaC technology which help us to the onboarding qlik tasks in more configurable and manageable way.

Consider a scenario of disaster recovery. If we are creating the json's on the file and we dont know the previous state of the task and recreating the task would be painful.

[OritA]

Hi, 

As this is out of the scope of QEM product, please contact Qlik Professional Services team to see if they can help you  to achieve your need. 

Regards,

Orit

[Dana_Baldwin]

Hi @Rak 

In addition to Orit's suggestion to engage with our Professional Services team - if you feel there is a feature missing from the product, please submit your idea directly to our Product Managers here:

https://community.qlik.com/t5/Ideas/idb-p/qlik-ideas

Thanks

[deepaksahirwar]

Hi @Rak ,

Welcome and Thank you for reaching out to us on Qlik Community.

There isn’t a direct integration of Qlik Replicate with Terraform or other Infrastructure as Code (IaC) technologies for the purpose of task management.

However, you can consider the following approaches:

• Version Control Systems (VCS): You can store your Jinja templates and generated JSON files in a VCS like Git. This would provide you with traceability and version history. You can then use Jenkins to pull the latest version of your tasks from the VCS and import them into Qlik Replicate.
• Qlik Replicate APIs: Qlik Replicate provides APIs that can be used to manage tasks programmatically. You could potentially write scripts or develop a custom application that uses these APIs to manage your tasks in a more configurable manner.
• Disaster Recovery: For disaster recovery, you might consider using Qlik Replicate’s built-in recovery options. Additionally, you could store a backup of your Qlik Replicate configuration (including tasks) in a safe location. In the event of a disaster, you could restore your Qlik Replicate instance from this backup.

I hope this helps! Let me know if you have any other queries.

If our response has been helpful, please consider clicking "Accept as Solution". 
This will assist other users in easily finding the answer. ‌

Best Regards,
Deepak Ahirwar