Passing "environment" as extra-docker-config

[mrcghil]

It would be useful to have the ability to set environment variables inside a container without having to rebuild a container locally.
I have implemented a solution on a fork and I am happy to create a pull request for this. Is there a strong reason for this feature to not be availabe to everyone?

Thanks,
Marco

[cry-wolf]

Love this idea, would help me tremendously

[Martin-Molinero]

Hey! Interesting idea, mind clarifying what's the user case for the environment variables?

[mrcghil]

Hello Martin,
Great to meet you! We wanted to have a way to pass configurations that:

• could inject configurations dynamically if we want to run many backtests in parallel or maybe point to different external services (e.g. BACKEND_URL, DB_CONN_STRING, ...). The config.json way of passing parameters feels a little restrictive.
• could work outside the class built on QCAlgorithm (this is less important for us ATM)

An alternative, could be to dynamically create config.json files and then specify which file gets picked by lean. This feels like a more contrived approach as it requires more code from the user and a bigger code change within lean.

Let me know what you think and if you have any reservations.
Best,

Marco

[mrcghil]

Hello Martin,
Added the PR here for your consideration: #567
Best,
Marco