You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Kedro viz extension in VScode doesn't start if environment variables are to be loaded from .env or any other file nor there is a way to specify how to load them.
Kedro and Kedro viz works normally cause they are run from a terminal that have already loaded the variables.
Maybe there is a way to specify the shell environment when launching a VScode extension.
Steps to Reproduce
Create a starter project
Define credentials.yml with any environment variable ${oc.env:AWS_ACCESS_KEY_ID}
Expected Result
Env variables are read correctly
Actual Result
It raises an exception
Kedro-Viz: KeyError raised while resolving interpolation: "Environment variable 'AWS_ACCESS_KEY_ID' not found"
Kedro version used (pip show kedro or kedro -V): 0.19.10
Kedro VSCode version used: 0.2.3
Python version used (python -V): 3.11
Operating system and version: MacOS
The text was updated successfully, but these errors were encountered:
For anyone interested, it seems that executing vscode extensions from terminals are almost impossible but it's possible to launch vscode from a shell where env variables are already defined, then all new terminals and extensions in that instance of vscode will have them preloaded.
So basically install globally dotenv and launch vscode like this:
Description
Kedro viz extension in VScode doesn't start if environment variables are to be loaded from .env or any other file nor there is a way to specify how to load them.
Kedro and Kedro viz works normally cause they are run from a terminal that have already loaded the variables.
Maybe there is a way to specify the shell environment when launching a VScode extension.
Steps to Reproduce
Expected Result
Env variables are read correctly
Actual Result
It raises an exception
pip show kedro
orkedro -V
): 0.19.10python -V
): 3.11The text was updated successfully, but these errors were encountered: