Project-level Environments

[GitPhule]

I would like to request Project-level Environments (or even Global environments), so that variables can be shared across all collections within the same project (or all projects).

I (presumably like many) am a recent Postman-refugee, and one of the things I had routinely used were global-level environment variables to store common base URLs (local test machine, DEV/TEST/STAGE/PROD environments, etc), which are common to all of my collections. Right now I had to duplicate these in each collection within the project in Insomnium.

Thank you for this consideration, and thank you for undertaking this!

[archywillhe]

hey thanks for the suggestion! do you commonly use an .env file (or .env.local, etc) for that? Insomnium will be transitioning to be filesystem-based and I think one thing I can opt in by default is reading from .env files

[archywillhe]

(or do most of you prefer a GUI solution? Just wondering.. thanks!)

[GitPhule]

Previously it was just in a Postman Environment (which appear to always be global). Whatever Environment you selected in Postman would drive the values used in the requests. Of course, maybe I was not using Postman correctly.

Currently, in Insomnium, I imported all of my Postman collections into a single Project. But, I had to duplicate ALL of my environment variables into each Collection's "Base Environment", which will be a pain to maintain when something changes in my environment.

I personally can live with .env files/folder structure (especially if there is a different .env file per environment), since it would be easy to store collections/files in the proper hierarchical structure for those collections that need to use them.

But of course a GUI solution is always nice, too! :)

[archywillhe]

ooh gotcha! thx for telling me about ur use case in such details:)) I will see what I can do for future users coming from post-man;

for now I'll be rolling out support for a global&individual .env first && and then gonna see how to best do the GUI