Best Practices and Guidance on CI/CD Implementation for IIQ

IdentityIQ (IIQ) IIQ Discussion and Questions
,
1

Which IIQ version are you inquiring about?

8.4p2

Share all details about your problem, including any error messages you may have received.

IHAC requesting best practice assistance regarding the following. Never tried this Forum before so hoping to share and pass along the information to them:

we are currently working on implementing a CI/CD pipeline for My7Access (our SailPoint IdentityIQ implementation), and as part of this initiative, we are leveraging the SailPoint Services Standard Build (SSB) framework to automate configuration and code deployments.

We have designed the pipeline with the following approach :

Our Planned CI/CD Workflow

  • Detect changed configuration files during merge requests

  • Validate the modified IIQ objects

  • Invoke SSB to build the deployment artefacts

    • Subset builds (for configuration updates)

    • WAR generation (if UI components need to be updated)

  • Upload the generated artifacts to the My7Access application server

  • Perform automated backups of existing objects on the server before deployment

  • Use IIQ console to import configuration updates

  • Deploy WAR if applicable

  • Promote the same artefact to other environments with controlled approvals.

We aim to fully automate the Dev → Test → Prod pipeline while ensuring safe deployment practices, consistent artifact promotion, and adherence to SailPoint’s recommended standards.

Request for Support

To ensure we are following SailPoint-recommended best practices, could you please assist us with the following:

  1. Validation of our proposed CI/CD approach

    • Is this pipeline design aligned with SailPoint’s recommended implementation pattern?

    • Are there areas where we should modify the process to improve performance, safety, or maintainability?

  2. Best practices for CI/CD automation in IdentityIQ.

    • Recommended folder structure within Git

    • SSB usage guidelines (subset builds, tokenization, ignore files, WAR builds)

    • Deployment order or dependencies we should be aware of

    • Backup and rollback recommendations

    • Any limitations when executing imports via automation

  3. Any reference documentation, sample pipelines, or architectural guidance that SailPoint can share to support a robust CI/CD implementation.

We want to ensure that our automation strategy aligns with SailPoint’s standards and avoids any potential pitfalls, especially regarding configuration consistency, tokenisation, and deployment safety.

Any support, documentation, feedback, or recommendations from your side would be extremely valuable for us as we move forward.

Thanks in advance for your guidance and expertise. We look forward to your insights to help us build a reliable and SailPoint-compliant CI/CD pipeline.

2

There are videos from SailPoint on this subject : https://youtu.be/CHVstm7ZT5U?si=ZHVD2pOl6qJl54QQ.

we built our own in Azure Devops but I’m not sure I can share them . Will need to check on that.