1
Redesign the environment variables
Source: Kong/insomnia#7813 · opened by @stebberg
As a user I would like to handle environment variables much easier and not to have duplicates. This might needs to redesign the way most of today's rest clients use environment variables. We can split this into 2 parts. 1.) Problem: All environment variables should(?) most likely be used in every environment, right? So why do I need to re-add the variables in every environment? If I need a new variable in my project, then I need to copy paste the same variable (name) into every(!) environment. Suggestion: Add all variables ONCE in the base environment - with or without a value. Now, in every sub-environment, you should not be able to add more variables - only set relevant VALUES to this pre-generated list of available variables (from the base). 2.) Problem: I need to have a lot of copies of the exact same environment variable in my environments. For instance if I have a STG environment, and in STG I have 3 servers (1 gateway and 2 front servers). In some cases I need to…
No pledges yet. Be the first to back this.
Comments
Similar requests
Collection Specific Environment Variables Superseding Active Environment Variables
2 votes · 0 comments
Allow Environment variables as command line params to inso cli
7 votes · 0 comments
JSONPath/XPath access to Environment Variables
1 vote · 0 comments
Right Click Set Environment Variables
2 votes · 0 comments
New shortcut for Base Environment and/or mask Private environment variables on dialog open
2 votes · 0 comments
No comments yet.