I'm trying to refactor my self-hosted dagster instance so that it uses multiple code locations. This is all fine and dagster/dagit sees the code locations and loads in the assets/jobs. However, setting up resource attributes only works when the .env file is in the module directory. Otherwise, dagster doesn't create the environment variables from the env file. While this might be more of a docker-compose and/or dockerfile issue, I'm looking for a solution that would enable me to keep both a single .env file (used by multiple code locations) and a single private key (for connecting to Snowflake) in a location that will be found and recognized by the dagster modules in multiple code locations. What is the best way to solve this issue? I tried creating symlinks to the files, but so far, the only thing I've found, is to create hard links (

ln /dir/to/myfile.env myfile.env

) in the code location module parent directories...