Leveraging SailPoint IdentityIQ and Docker for seamless development

Description

This session explores containerization, focusing on its usage with SailPoint IdentityIQ to streamline development and production workflows, ensuring consistency and security across environments. Attendees will learn best practices for using Docker, from creating Dockerfiles to implementing CI/CD pipelines, to enhance software development efficiency and deployment.

8 Likes

Here are the files used during the session:

1 Like

thank you! My Docker based IIQ 8.4 is running… how nice and easy :grinning_face:

1 Like

This is really useful. Though I didn’t know much about docker, I configured iiq 8.4 after watching your video. Thanks a lot for such valuable insight !

The only thing I modified is renaming file .env.simple to .env as I got error while staring composes. Hope this would help for others too!

Firstly, great intro presentation to containers. I definitely agree with advantages for upgrades/patches, either IIQ or SW. Once you have the deployment infrastructure in place, it is way simpler as you said. Would be great to have it - don’t currently have it.

For the regular feature/fix releases, I wonder if there is advantage if you use mainly XML objects without Java classes. There is usually mix, but a lot of code is maintained in XML objects.

I guess you could always have one image set up for import custom-init for new deployment and restore? Would it be like that or do you have different experience or suggestion?

That also brings me to a comment for different environments and different versions. I believe it works with different versions quite well as you mentioned. For example when you preparing for upgrade or testing various versions.

For different environments, there is usually “no problem” with the code, but code issues related to data, infrastructure and setup. Not sure if the joke “it works on my pc” works here as the containers would not really help if you have only IIQ servers. Do I assume correctly, that if you do IIQ as containers, you would also use containers for target systems/HR and other elements for lower environments? How do you reduce data issues between PROD and lower environments in these cases? Any suggestions?