CI/CD best practice approach to store ISC Objects Deployment to GIT

[pateldivyang0319 (Divyang Patel)]

Hi SailPoint experts, I am looking for best practices or recommended approach that we can use to store the ISC objects to centralized version control like Git to keep tracking of all history, backups on timely schedules. Are there any relevant documents that I can refer to ?

Right now, I am using Config Hub to promote changes from one environment to another environment but based on Client needs, we need to store all ISC objects to Git possibly.

Thanks,

Divyang Patel

[Gopi2000 (Gopi S)]

Hi @pateldivyang0319,

Kindly have a look at the following SailPoint Developer Community discussion. It covers using ConfigHub with CI/CD and GitHub Actions for change management and version control:

SailPoint Community – ConfigHub in CI/CD

SailPoint ISC → ConfigHub/API → GitHub → GitHub Actions → Target ISC

1. Export ISC objects using ConfigHub/Config APIs.
2. Store the exported objects in a centralized GitHub repository.
3. Use Git to maintain version history, backups, and change tracking.
4. Developers make changes through Git branches and Pull Requests.
5. GitHub Actions automates backup, validation, and deployment.
6. Approved changes are promoted between ISC environments.
7. Previous Git versions can be used for rollback/recovery.

Hope this helps.

[patrickboston]

I built an open-source tool that may be able to help you with this.

Introducing ISC ODT (Identity Security Cloud Object Deployment Tool)

Hello everyone, I’m excited to share ISC ODT (Identity Security Cloud Object Deployment Tool), an open-source utility designed to help teams manage and promote SailPoint Identity Security Cloud (ISC) configuration across environments. I’ve built this in collaboration with Justin Sewell (@jsewell). After working on numerous ISC implementations, one recurring challenge has been managing configuration changes between sandbox, test, and production tenants. While ISC provides powerful APIs, deployi…

[Abhi_Mandakki (Abhishek Mandakki)]

Philip has provided one of the best way for CI CD practice and the best thing is we will have backup of all the objects.

ConfigHub in CI/CD: Change management via code with GitHub actions - Content / Video Library - SailPoint Developer Community

[kannan_sb85 (Kannan Sriniyappan Balakrishnan)]

@pateldivyang0319 -

I would consider Patrick’s tool. It is an open-source utility, purpose-built for this exact scenario. There is a good chance it would eliminate the need to write your own tooling, though there is always a risk of a niche edge case. The main thing to consider for a regulated client is the trade off between community & maintained tooling as part of the deployment pipeline, versus supported SailPoint tooling (CLI/API).

If the client has change control requirements around tool provenance, they may prefer the CLI + GitHub Actions combination as its easier to defend during a security review.