With all the ongoing changes related to the API (mostly due to the deprecation process) is there anyway to track changes to the Postman collection? I know we had this originally, but I believe something in the process changed a while ago that “broke” the “pull changes” option and instead we now have to just re-download the full collection every time which is a challenge from an auditing perspective as well as ensuring any needed customizations/copies get moved to the new collection every time.
I’m familiar with the process described, but I believe the collections are getting deleted/recreated giving them a different GUID which causes this process to not be available.
Currently, our collections are too large to be able to be updated via the postman APIs, so whenever a change is made, they are deleted and re-uploaded. There are two problems with the postman collection APIs today with our large collections
- If we try to update, then it times out
- Even if we do get it to update (via incremental changes to each endpoint) then when you try to pull on larger changesets, it crashes the postman client tool.
Because of these issues, the only option we have at this time is to completely delete the collection and create a new one.
However, there is a good option available for seeing changes to the APIs. You can watch the GitHub repo here: GitHub - sailpoint-oss/api-specs: This repo houses the API specifications for all SailPoint services. This will ensure you are notified of any changes made to the API specs.
@philip-ellis - Thanks for the update and explanation. Unfortunate side-effect of the tools involved, but understandable.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.