postman-app-support
postman-app-support copied to clipboard
Allow multiple environments to be selected for a request/collection/monitor
Is your feature request related to a problem? Please describe. I have one set of environments for Testing/Stage/Production, and one set of environments for different devices - Android/iOS. I'd like to mix-and-match environments while making requests: Stage+iOS / Production+Android, and avoid creating 3x2 environments to test each combination.
Describe the solution you'd like Allow the Postman runtime to accept multiple environments while running a request/collection/monitor.
It would be very helpful to have multiple environments that you could select for an API. For example, we have a set of stacks to test against: Test1, Test2, Staging, Production, etc and have different environments setup for each stack. We also have multiple devices, customers, etc that we use for testing each with their own set of variables. I'd like to be able to select multiple environments at a time. [Test1, Device1], or [Staging, Device2, Customer5]. The way it is now, I have to have multiple environments with duplicate variables i.e. Test1_Device1, Test2_Device1, Staging_Device1, Test1_Device2, ...
I'd really like this too. My company is moving towards using more environments (dev, staging, on-prem prod, AWS east, AWS west, etc), and I'm getting involved in multiple projects, so I'm looking at more like 10x5 environments to really use postman everywhere I need to. My environments list is getting unwieldy, and it's annoying to realize "oh, I don't have an environment for service X in environment Y" when I need to make a REST call.
This is really a must have feature. I tried this in paw and it was really helpful. Can we please have it in postman.
This is a feature that I very much desire
Is this so complicated to implement? There are plenty of use cases..
Any update on this request?
+1
This would be very useful.
+100
Bump. This would be brilliant to split out a very large and varied list of environment variables
+++++1 for this to be added, ugggg
It's pretty dumb that there is no way to copy/paste specific variables, or a set of them.... even if we could just view/edit the JSON in the app we could much more efficiently manage these!
@cajuncoding thanks for writing to us on this thread. We acknowledge that this problem has been highlighted for a while.
We do not support view/edit json in the app to manage the environments. You could export environments, make edits and import them back.
However, I would suggest that a better way would be to just use the 'Duplicate' option to make a copy of the entire environment. You would have to then disable/delete the variables that are not needed in the copy. This will hopefully help you solve your usecase.
Do let me know if this helps.
We will definitely be looking into this problem more closely and sharing updates.
@malvikach I see that you replied for a different subject than the very first post. Since you are product manager at postman, may I ask you if the ability to make a request using multiple environments in postman will be added anytime soon?
Thanks.
@oguizol We do not have this in our immediate short-term plans. However, it will help me if you are willing to spare some time and talk about this with me.
If this sounds good and if you are interested, please send me your details here and I will coordinate a time to speak with you. Your feedback will help us understand this need better and expand on it further.
Be able to select multiple global environments would be VERY useful!!
+1 Being able to configure a workspace environment selecting many environments would enable to maintain the core configs used on requests and specific ones, regarding person and/or team on apart, which would result in an easier way to interact with APIs through an user perspective.
+1 on this. Any ETA?
+1
+1
+1
Would be awesome to get that feature. Because Insomnia is able to do this, but I'd like to avoid the need to migrate...
+1
+1
+1
This is a most wanted feature and after 4 years, still no plan... Too bad
This would be super helpful to keep environments dry!
Yes plz
It would be very helpful not only for combining environments and type of tests but any other orthogonal namespaces, like set of business logic constants. Also our tests are interacting with multiple sources and destinations and their combination is much more then n*m.
@malvikach Please, pay attention.
Running tests in postman app and in CI - being able to select multiple environments would help greatly with credential security.
inability to use several environments kills postman for me: instead of defining additional environments, I have to create duplicate collections. I agree with the others that this feature is very much needed.