Do we have idnow documentation for Deployment, migration and Artifacts management?

I found the documentation for IIQ for code management.
https://community.sailpoint.com/t5/Technical-White-Papers/Best-Practices-Deployment-Migration-and-Artifact-Management/ta-p/75804
Wondering if we have same kind of document for IdNow as well.

Hi @ganesh-kandel5050

Welcome to the Dev Community :slight_smile:

I’ve found these articles which may be helpful:

https://community.sailpoint.com/t5/Implementation-Resources/Technical-Implementation-Resources/ta-p/226750

https://community.sailpoint.com/t5/Implementation-Resources/Project-Management-Resources/ta-p/226751

https://community.sailpoint.com/t5/Implementation-Resources/Program-and-Strategic-Guidance/ta-p/226752

There is no equivalent document for ISC. However, the same principles can be applied:

  • The JSON representation of your configuration objects (Sources, Roles, Identity Profiles, Connector Rules, etc.) and the XML files for Cloud Rules can be exported and stored in a code versioning system (such as GitHub)
  • An automated CI/CD process can deploy changes via REST APIs to the tenants
1 Like

Hi @ganesh-kandel5050

Welcome to SailPoint Developer community.

You can use VS Code Extension to get the config files, not all objects are supported though. Currently support objects are

  • Sources
  • Transforms
  • Workflows
  • Rules
  • Service Desk
  • Identity Profiles
  • Access Profiles
  • Roles
  • Forms
  • Search Attribute Config
  • Identity Attributes
  • Identities

Please note that IDN VS Code Extension keep gets updated with new features. This might be enough in coming days for all the requirements with respect to the repository. But I would say these objects for enough for now.

You can use config hub as well for backups and deployments in different tenant.

For the objects that are not covered, you can make use of APIs, write simple scripts in PowerShell or Python. We do have CLI and SDKs

You can use Git for versioning, we do have APIs to manage the objects, so you can build CI/CD process by making use of those.

Thanks
Krish

I just found this article for ISC, which does seem to be more or less the equivalent of the Migration Best-Practices for IdentityIQ: https://community.sailpoint.com/t5/IdentityNow-Articles/SailPoint-SaaS-Change-Management-and-Deployment-Best-Practices/ta-p/189871

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.