[BUG] Traversing for .databricks.env from notebook init scripts has unintended sideeffects
kartikgupta-db opened this issue · 0 comments
kartikgupta-db commented
Describe the bug
We are traversing up to find a .databricks/.databricks.env file. This can lead to unintended cases where a user opens the root folder with the extension, leading to creation of the .databricks folder. Any subfolders will always load this .databrick.env now and it will not be possible to NOT use databricks.
This was done since loading env variables from a python.envFile was not very reliable for vscode notebooks. But this was fixed in a recent fix microsoft/vscode-jupyter#14105. We might be able to safely rely on these env vars now.