[BUG] setting databricks.python.envFile is unknown

[copdips]

Describe the bug

I'm trying to use local .env file with the setting databricks.python.envFile as per extension doc described here. But in VSCode there's no such settings, and by manually adding the setting in the file settings.json, VSCode warns that the setting is unknown.

Screenshots

System information:

vscode and databricks extension both are latest

[ilia-db]

Hi, our docs are outdated there - we no longer expose the databricks.python.envFile setting. But you can set the python.envFile to your desired path (we read it too and update our internal env var representation, which we use for "Run with DBConnect" commands or for type: 'databricks' launch configs).

Does it cover your use case?

[copdips]

Thanks for the prompt reply.
Could you please give a example on how to get the env var in the code ?

for example, under the root of my repo there's a file .env with content:

AA=11

the .env file is specified by the python.envFile VSCode setting.

When I run type: 'databricks' launch configs, from the debug console, os.getenv('AA') returns None.

[ilia-db]

Sorry for the confusion, type: "databricks" executes the file remotely, and we indeed don't read env file in this case. We do pass over env vars from the env section of the launch config:

For local runs (Run/Debug with Databricks Connect commands) we load the vars from python.envFile.

You can also "extend" local python launch configuration by adding "databricks: true" to it, which will ensure we execute the local files with our bootstrap logic and load the env vars (but our internal DATABRICKS_* vars to make sure dbconnect can access remote workspace, plus the things from python.envFile)

(side note, "python" launch type is now deprecated, but we don't yet support "databricks: true" field on debugpy config)

[copdips]

Thanks a lot, this is working now !

Regarding the local Python launch, I tested both "type": "python" and "type": "debugpy", and they both work, althought there's a warning for each:

[ilia-db]

Should be fixed after we merge and release this: #1465