topic Re: Automation for Backing up Qlik Applications in Github in Qlik Automate

Automation for Backing up Qlik Applications in Github

FranciscoQ — Fri, 14 Jan 2022 21:04:46 GMT

So I create this automation, which basically every time an up is published, will take some information from the app, like the name and space name, it will export the app without data, will have a variable with the date when the app is being published and then will create a backup of the app (without data) in Github. This is very important to have previous versions stored in case we change something from the app, we publish it and then if the last changes didn't work well, we can go back in time to previous versions.

So the variable block it has a date function:

And then, the "create file content block" of GitHub: Will have the user and repo name, and the path will be Space Name / APP Name & Date. So for each space, I will have a list of the apps published with the date and time, so I have the complete history of all the versiones published.

The versions will be stored inside the directory with the name of the space, and inside the directory will be all the apps from the space, with the different versions of when the app was published:

First of all I would like some feedback of the automation. What things I could improve.

Second, I was thinking to create an automation that publish all the apps from different spaces into managed spaces. I wonder what will happen with this automation to create backups, since it start running every time an app is published (webhook run mode). Will create like a queue of the apps that has to store in github, or will be interrupted every time a new up is published before the previous one has been stored ? (In case the action of publishing finish before the app is stored in githun, maybe I could put both actions (Publish and Backup in Github) in one automation.

Thank!

Francisco

Re: Automation for Backing up Qlik Applications in Github

Vinay_B — Sun, 16 Jan 2022 16:40:46 GMT

Hi @FranciscoQ ,

Please check this post: https://dataonthe.rocks/whats-in-it-for-them/

It has a detailed flow on how to build the automation for backing up apps to Github.

I hope this helps!

Re: Automation for Backing up Qlik Applications in Github

PietMichielRappelet — Mon, 17 Jan 2022 07:43:15 GMT

Some additional links that can help you:

Github related articles: Connector overview page > github icon: https://community.qlik.com/t5/custom/page/page-id/Connectors
- getting started: https://community.qlik.com/t5/Knowledge/Github-How-to-get-started-with-Github-in-Automations/ta-p/1840171
- backup and version your apps with Qlik Application Automation: https://community.qlik.com/t5/Knowledge/How-to-Qlik-Application-Automation-for-backing-up-and-versioning/ta-p/1835917
We also recently released a more complex template for committing your app to github: https://community.qlik.com/t5/Knowledge/CI-CD-pipelines-for-Qlik-Sense-apps-with-automations-and-Github/ta-p/1860837

hope this helps.

Re: Automation for Backing up Qlik Applications in Github

Harsha-Lodha — Fri, 26 Jul 2024 14:12:39 GMT

@FranciscoQ This is very great automation. I am working on building something similar. But I am not able to find way to get triggered when app is published. May I know where is the first block you used? "App Published". Thank you!

Re: Automation for Backing up Qlik Applications in Github

OdieW — Thu, 01 Aug 2024 18:53:10 GMT

I'm sure you've figured this out by now, but for anyone else finding this post with the same question, the App Published block is just the initial block from a new automation. To get it to be App Published you choose webhook, then qlik sense cloud connector, then when an app is published.

Re: Automation for Backing up Qlik Applications in Github

Harsha-Lodha — Thu, 01 Aug 2024 19:47:23 GMT

Yes I figured it after a while. Also apart from this I have another question about importing qlik apps from github. I was able to design an automation to import from github. But I am confused about the "import App from base 64 encoded file" with Autoreplace mode.

I understood how the block works in import mode as NEW. It imports the required app with app name given in the 'target app' field. And app is imported in the space as per field 'space id'. App id field is not used in that case.

But what happens I use import mode as Autoreplace?

Does my App which has same app name as 'Target app' field from the space mentioned in 'Space Id' field gets replaced by imported app completely? Or does it merges with imported app with Target app? And what does App Id field is used for? Please describe autoreplace mode in detail. I want my target app to change completely as per imported app. But I don't want my target my app id to change. But in reality I when I sue autoreplace mode instead of replacing my existing my target app, automation creates new app with same name target app. Thank you in advance.

Re: Automation for Backing up Qlik Applications in Github

Dave_Channon — Mon, 05 Aug 2024 08:05:12 GMT

Hi @Harsha-Lodha the autoreplace function is an internal method, and isn't usable via external API calls. Please see the documentation on that API endpoint here.

Re: Automation for Backing up Qlik Applications in Github

Harsha-Lodha — Mon, 05 Aug 2024 14:54:55 GMT

Hey @Dave_Channon,

Thank you so much for the explanation. If the Autoreplace option isn't for external calls, could you explain why it's included as a mode option? Will it be available for external API calls in the future? If not, is there another way to replace an existing app with an imported one?

Thank you!

Re: Automation for Backing up Qlik Applications in Github

Dave_Channon — Wed, 07 Aug 2024 12:45:03 GMT

I can't comment on why it was added, but I'll raise a request to remove it - thank you for the feedback there.

There is no clean way to overwrite an app in a personal or shared space while maintaining the ID.

(There is a hacky API way, where you can move the app to a managed space, import the new app, publish over the app in the managed space, delete the imported app, then move the managed space back to the original space...)

Re: Automation for Backing up Qlik Applications in Github

Harsha-Lodha — Fri, 16 Aug 2024 13:52:34 GMT

Hello @Dave_Channon ,

Thank you so much for the explanation that really helps. While we have our daily backup going on. I get this one error randomly sometimes for random app. The backup for same app happened successfully next day or day before. Can you please tell what causes this error. Also how can I handle this. Thank you!

Main error stays same

Details from chronological section changes everyday for random apps

once I got this

Once I got this

Re: Automation for Backing up Qlik Applications in Github

OdieW — Fri, 16 Aug 2024 13:48:02 GMT

@Harsha-Lodha Does that app happen to have section access? I'm not using this specific automation, I am using the one from the template and have modified it, but I was getting this error when my automation tried to export the load script. I found it was due to section access, which makes sense because only the tenant admin can export apps with section access and only from their personal space. That being said mine failed every time with this error, until we commented out the section access, not sure why yours would work some days and not others if its the same issue. Hope this helps and hope you can figure out whats causing it if its not this.

Re: Automation for Backing up Qlik Applications in Github

Harsha-Lodha — Fri, 16 Aug 2024 15:50:42 GMT

Hello @OdieW ,

My app doesn't fail due to section access. I have a condition to skip apps which has section access. Also my automation does backup for 200+ apps. And randomly one day app a will fail and next day app b will fail. And some other time everything just runs fine.