This demo shows how to use SailPoint ConfigHub in a CI/CD environment with GitHub Actions and GitHub as the change store. ConfigHub provides backup and restore for your tenant data; its APIs integrate with your pipeline so you can manage all your objects as code and enforce change management through your existing Git workflow.
This is really helpful and I am able to set it up quickly. One thing I see is it is not backing up as per the cron expression but takes the backup when clicked on run workflow manually. Anything specific needs to be checked?
The workflow is designed to run automatically based on the configured cron expression. The manual Run workflow option is only for on-demand execution or testing. Once the scheduled time defined in the cron expression is reached, GitHub Actions will trigger the backup automatically.
Agreed, after altering the Cron expression It is running as scheduled.
Thanks.
I am facing a major issue . It is only backing up to 1000 objects and omitting the rest.
Please provide your suggestions.
Hi @philip-ellis ,
Please let me know if something needs to be changed
Hey @Abhi_Mandakki,
I believe this is just a display issue, Github truncates the view when there are many objects to display. The objects should still be committed and stored properly! You can verify this by cloning the repo locally and verifying all the objects are there.
If you clone the repo and the objects are missing, we can dig in further!
Thank you @tyler_mairose ,
You are right. We don’t see all the objects in GITHUB UI.
I’m glad to hear it is functioning correctly!
As you use this feature, we would love to hear your feedback on what you like and what you might like to see in the future 
Hey @tyler_mairose , When there is/ are password policies without assigned sources in tenant the provided backup ps script is failing, i went and changed few lines to skip these password policies in another tenant I tried by deleting the password policies without assigned sources
Thanks in advance
Avinash
@philip-ellis I am currently trying to install the UI Development Kit by following the instructions provided in the video tutorial. However, when I run the “npm install” command, it removes all modules from the “npm_modules” folder. I believe some of these modules are required for the application to run correctly, such as “concurrently”.
I am seeing below error when the installation is complete:
'npm error code UNABLE_TO_GET_ISSUER_CERT_LOCALLY
npm error errno UNABLE_TO_GET_ISSUER_CERT_LOCALLY
npm error request to https://registry.npmjs.org/zone.js failed, reason: unable to get local issuer certificate
npm error A complete log of this run can be found in: \npm-cache_logs\2026-09-16T08_40_03_537Z-debug-0.log’
It seems it cannot verify the certificate from registry. So, do we have to manually import the Sailpoint Certificate in our machine?
Also, I noticed this issue when I attempted to start the application using “npm run start” and received the following error message:
npm run start
sailpoint-ui-development-kit@1.4.1 start
concurrently “npm run ng:serve” “npm run electron:dev” --names “angular,electron” --prefix-colors "#5C44E4,#FF3E00"
‘concurrently’ is not recognized as an internal or external command,
operable program or batch file.>
As this is my first time working with the UI Development Kit, could you please help me understand if I have missed any steps during the installation process or if there is something that I may have configured incorrectly?
Any guidance or troubleshooting suggestions would be greatly appreciated.
Thanks in advance for your help.
It sounds like this is an issue on your local machine. NPM is attempting to connect securely to the registry, but the SSL certificate verification is failing.
This is highly common in corporate environments where IT security proxies or firewalls intercept network traffic using self-signed corporate certificates that Node.js/NPM does not trust by default.
To get unblocked, you can try the following solutions:
Option 1: Point NPM to your system/corporate CA cert (this is the best option)
Option 2: Use the standard OS keychain using NODE_EXTRA_CA_CERTS
Option 3: Disable strict SSL check (Temporary workaround only and not really recommended, but will get you past the issue most likely) npm config set strict-ssl false
you might need some help from IT to incorporate option 1 properly as they will know where the CA cert is located.
Thank you, @philip-ellis, for your help. That was helpful. I have one more question.
In the UI Development Kit, under the Config Hub tab, I’m trying to configure a repository, but it isn’t working. I’m using GitLab, while the configuration instructions appear to refer only to GitHub. Does this configuration support only GitHub, or can it also be used with GitLab?
Also, after completing the configuration and refreshing Object Types, nothing appears—not even an error. Is there a way to check what happened or troubleshoot the issue?
