Is your feature request related to a problem? Please describe.
It would be great if I could have a private base environment for sensitive information.
Describe the solution you'd like
I provided a potential solution here, in that there could just be a second "secrets" base environment that is private.
Describe alternatives you've considered
The alternative looks to be implementing each environment that I'd like as secret, which does not work because I want to share regular environment details with teammates.
Additional context
Context is available in the Question I asked here
It would be very useful!
Thank you!
Hi @rbrianhazzard and @alexandrim0, while private base environments are not supported yet I do have a proposed solution in https://github.com/Kong/insomnia/issues/2593#issuecomment-690679032 using .env files. Let me know if that works for your use case?
This way, none of your secrets are actually _in_ Insomnia - just pulled in from private .env files on your filesystem. But the structure of environment variables will be shared across your team.

Hi @develohpanda, that looks great. I'll try it out today but looks like it should be a suitable workaround for what I was asking.
It looks too complicated.
Maybe I can use this.
But my colleagues won't.
I'd rather wait for the update.
Thank you!
No worries! I'm not sure we can provide an ETA on if or when something like this might be included in the core application.
The only thing your colleagues will need to do, once you have set up the workspace and environment, is specify where the .env file exists (on their filesystem), and install the insomnia-plugin-dotenv plugin. 馃
I will try this at some point.
Thank you!
Hey - this works for my usecase. I will close the ticket since there's a workaround now via the plugin