Automatically sync Postman collections or similar Executors

[vsukhin]

In a company with multiple developers and hunderds of api methods postman collections can be updated quite frequently, including different testing env. Exporting/importing them each time can be really inconvinient and most probably they will be not synced most of the time. Add sync process either before script execution or on some schedule, ideally on webhooks if postman supports them

[olensmar]

Thanks @vsukhin - Postman-cloud has the possibility to automatically push updated collections to a github repository - so that is one way to achieve this - together with a tool like ArgoCD that would then sync these collections as scripts to the cluster containing TestKube. Another approach could be for the postman script to contain a reference to the collection in postman-cloud (instead of the collection itself) and pull it from there one execution (via the postman-cloud REST API) - this would require the user to provide a corresponding access token (stored in a secret?) for these API calls!?

[vsukhin]

Yes, I meant the second option, this is how it was done in my personal experience with integrating it into CD github action. A token was stored in github secrets. But might be, the first option can also be useful, if it's secure enough and we have github inegration for Cypress

[olensmar]

great - I think we should support both options.. the first caters to a GitOps workflow and makes the collections part of your cluster state, ensuring that you are always able to run them (since you are not depending on access to postman-cloud at test-execution time), the second is probably more "fluent" as it doesn't require the syncing processes with CD..