Share all details about your problem, including any error messages you may have received.
We’re running SailPoint IIQ 8.3p5 and maintain our configuration and code using an internal Git repository with SSB packaging. Unfortunately, our Git repo has not been consistently updated over time, changes were made directly in TEST and PROD without being committed back to Git.
We now want to:
Export all custom configuration and code (Rules, Workflows, Applications, TaskDefs, Roles, Forms, Policies, etc.) directly from our live environments.
Reconcile differences between environments.
Refresh and update Git so it accurately represents what is currently deployed, and re-establish it as the single source of truth for future deployments.
I’d like to hear from others who have tackled this:
What is the best approach for exporting objects?
Any lessons learned when reconciling across multiple environments?
How do you handle environment-specific details like endpoints or credentials?
Do you have any scripts, templates, or checklists that made the process smoother?
Any guidance or shared experiences would be very helpful.
I was many in this situation and in every case its a hard work.
For the export you can use this plugin that export all the object that you want.
The hard part starts now; the first step is to understand what is useful and what is useless. Usually in the test enviroment you can have a lot of code and configurations that you dont have in Prod and you dont have the documentation regarding that, its will be very difficult understand how that code is here.
Personally, I trust into Prod and I try to reconcile Test with it. In same case, my stes are those:
Export the code form each enviroment.
Upload everything on repo to have a “backup point” of current situation.
Find the difference between the enveriments using tools like WinMerge
Choose how delete and how maintain based on the documentation and the future changes
For your scenario with IIQ 8.3p5, here’s a practical approach:
Export Objects: Use the SSB provided exportscript to extract all objects in bulk (Applications, Rules, Workflows, etc.) for a complete baseline. For selective or individual object exports, the Export Objects plugin can complement the process.
Reconcile Differences: Compare exported XMLs from TEST, PROD, and existing Git using diff tools (Beyond Compare, WinMerge, or Git diff). Identify missing or modified objects and resolve conflicts.
Environment-Specific Details: Replace hardcoded values (endpoints, credentials) with placeholders in XMLs and maintain separate environment property files. Inject these during deployments to avoid overwriting environment-specific configs.
Refresh Git: Once reconciled, commit a full baseline to Git and use it as the single source of truth. Maintain incremental commits for future changes.