Multiple envfiles from launch.json

[andrewFirstResonance]

Hey all, I know this was a GitHub issue that was decided that there wasn't enough community support for a few years ago, but I do think this still would be a really nice feature to have. It's very common to have one env file git committed to a repo with either template values or safe generic values, and then another private env file that basically upserts over the existing env file with your own private values that are not git-committed. It's a nice workflow.

I've also seen flows like .env.base, .env.local. .env.production, etc. where .env.production is .env.base sourced and then .env.production sourced over it.

Hope that all made sense. Anyways, would love to see y'all reconsider development on this issue. Thanks!
#10142

[andrewFirstResonance]

I guess a solution could be to use python-dotenv to source env variables within your python code. I've also tried building a preLaunchTask that just sources my env files with a bash command, but I think the task runs in a different shell than my integratedTerminal.

[eleanorjboyd]

Thanks for the feature request! We are going to give the community 60 days from when this issue was created to provide 7 👍 upvotes on the opening comment to gauge general interest in this idea. If there's enough upvotes then we will consider this feature request in our future planning. If there's unfortunately not enough upvotes then we will close this issue.

[github-actions]

Thanks for the feature request! We are going to give the community 60 days from when this issue was created to provide 7 👍 upvotes on the opening comment to gauge general interest in this idea. If there's enough upvotes then we will consider this feature request in our future planning. If there's unfortunately not enough upvotes then we will close this issue.

[github-actions]

Because we have not heard back with the information we requested, we are closing this issue for now. If you are able to provide the info later on, then we will be happy to re-open this issue to pick up where we left off.

Happy Coding!