Open diegofernandon opened 1 year ago
+1
+1
+1
đź‘‹ hello from flows product team - thinking about this, would you want to run a flow that isn't published to run in the Postman cloud through the CLI. As in, the equivalent of clicking the run
button on a flow from the browser or the app, and passing a payload to it?
I think it would be great to have multiple options. I think one of them would be definitely to run same as RUN button. I would be very happy if there would be same solution as running entire collection (or part of it) in CI/CD. Did your team had any ideas or suggestions on how to run flows?
+1
Flows are good at the first glance, but useless in the long time period without the ability to use it in CI/CD. To be honest, today I've stopped my developers from using Postman flow when I've realized the lack of this feature. It is 'must have' feature - to be able execute flow from CLI, from CI/CD, also without connecting to a cloud for testing internal API.
+1
+1
Is there any update on this feature request?
It's definitely in the works but I can't share a timeline just yet.
+1, this will be a very useful feature!!
Is there an existing request for this feature?
Is your feature request related to a problem?
N / A
Describe the solution you'd like
Create a kind of integration between Postman CLI and Postman Flows in order to execute a Flow from Postman CLI. It would be useful for executing everything from the command line and also for integrating the flows execution to the Pipeline releases
Describe alternatives you've considered
A new CLI command option to execute a Flow form the command line e.g. Postman flows run "Flow-id"
Additional context
An advantage of executing workflows would be to have the possibility to automate them in our pipeline release, taking advantage of the current integrations. e.g. Azure DevOps-Postman CLI integration