I am trying to create a CI/CD framework for our IdentityIQ 8.2 and searching through the internet, there is no simple way to do it.
We are controlling the config files through SSB and updating it on a Git Repository. However, the file upload is done manually or through IIQAccelerator and this is rather slow and dangerous when uploading/updating numerous files at the same time.
I have found some articles explaining how to accelerate the process like this one from Sailpoint Technologies:
These articles involve building a war file and deploying it, however I have seen other saying it’s simple using the iiq console command and importing the xml directly.
Our ambient is composed by DEV, QUA and PRD and have several application servers for environment. Each environment has one database.
Has anyone ever created a CI/CD framework for IIQ? If so, can you help.
First of all, thank you for your help. I have a little question, in Ansible you download the base war and the custom zip from Nexus. Why both and not only the base war?
Another question is about the delta aggregation states. Are these related to the Delta Aggregation (Delta Aggregation) and why do you need to save these states before importing the xml files?
The base war doesn’t have any of our customizations, those are in the zip file. The base war is only downloaded and unpacked if that option was selected in Jenkins. In practice, we only need to install the base war when upgrading IIQ or applying an efix. That is one of the differences between DevSecOps toolkit and SSB (where the customizations are packaged into the war file).
The delta aggregation state is saved in the application object. When a deploy imports the application object, the delta aggregation state is “lost”. Depending on the application, delta aggregation won’t work again until a full aggregation is done. The save/restore is a work-around for that.
We’ve done similar things using IIQ to restore the application object data for deltas just using a service definition and keeping track of the deltas in a custom object so they can be referenced after a deploy and restored.