Enhancement: read .env files about eclipse-environment-variables HOT 6 OPEN

I'd like to import environment from an env file, but on a per launch configuration. My reasoning is that many times I need to simulate something running in a cloud environment with secrets.

from eclipse-environment-variables.

How would you see this happen?
What do you suggest?
Should it automatically read .env files?
Should it be an opt-in feature (globally or per project)?

from eclipse-environment-variables.

Thanks for asking. I have to admit that I did not use Eclipse recently. I changed to Visual Studio Code.

So my scenario is that I have a lot of projects, which are depending on environment variables. I have to switch between projects a lot. Variables often have the same name, but different values (e.g. HOST_URL)
Furthermore during development these env variables change quite often (e.g. new password for a service).
It is a hassle to keep all the variables up to date and change them in eclipse when changing projects.
Furthermore there are different .env files for different project environments (development, test, production)

So to not over-complicate things it would be great if one could configure a file per project to read env-variables from (auto import from file when opening project). So if I configure ".env", Eclipse tries to read that file from the project root when I open the project.

I have to admit that since I wrote this feature request I learned that Eclipse uses the currently set environment variables and I could just go into the project directory and auto-set the variables with dotenv or a start script and then start an eclipse instance from that directory instead of using the eclipse start menu entry.
I found that to be a good workaround.
So maybe if I am the only one with that need it's not worth implementing it.

from eclipse-environment-variables.

Thanks!

from eclipse-environment-variables.

This feature could be implemented as JetBrains Intellij IDE.

https://plugins.jetbrains.com/plugin/7861-envfile

from eclipse-environment-variables.

ut on a per launch configuration. My reasoning is that many times I need to simulate something running in a cloud environment with secrets.

Is gonna be great this way!

from eclipse-environment-variables.