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
