Seek Guidance on Automating GitHub Pull Requests for ISC Changes

Identity Security Cloud (ISC) ISC Discussion and Questions
,
1

Hi All …

Currently, we use GitHub actions/VS Code approach to make changes in ISC once GitHub pull request is reviewed and approved.

I am exploring options whether this GitHub PR creation step itself can be automated. Please correct me if I am wrong, SailPoint workflows do not have native GitHub actions support.

Questions around this;

  • I am wondering can this be achieved using SailPoint workflows & Forms in combination with a middleware (e.g Lambda function) to interact with GitHub APIs? Is this type of architecture supported and practical with SailPoint workflows?
  • Has anyone implemented a similar automation approach for ISC changes? If so, how did you handle auto GitHub PR creation and the main steps involved?
  • Are there any limitations, considerations or a better recommended approach?

I would appreciate any guidance around automating GitHub PRs.

Thanks

2

I tried similar process but could not automate fully, the reason is the dependency of one object on another one.
if you try to import multiple object to different types it need to go in particular order only otherwise it will fail.

1 Like
3

Thanks @vishal_kejriwal1 for sharing this info.

For others: if anyone has implemented or explored a similar approach e.g using workflows and a middleware to call GitHub APIs, Lambda functions, or another pattern, any insights on how you handled auto PR creation (and what worked / didn’t) would be highly appreciated!

Thanks