Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Environment variables are not being honored by extension #236

Open
pisymbol opened this issue Sep 22, 2023 · 0 comments
Open

Environment variables are not being honored by extension #236

pisymbol opened this issue Sep 22, 2023 · 0 comments

Comments

@pisymbol
Copy link

pisymbol commented Sep 22, 2023

Describe the bug
I have defined a .env file with name=value pairs that should be interpolated before up, down, operations. They work under okteto CLI but not through the vscode extension.

To Reproduce
Steps to reproduce the behavior:

  1. Create a .env file with OKTETO_NAMESPACE=foobar
  2. Create an okteto 2.0 manitest and use the namespace: "${OKTETO_NAMESPACE}
  3. Try to do an env up or down via vscode (okteto up and okteto down work on the command line)
  4. See error with something like Okteto down failed: Using ${OKTETO_NAMESPACE} ... and complains about permissions errors because it is trying to deploy to the wrong namespace (the string literal).

Expected behavior
The .env file should be evaluated BEFORE okteto actions.

Desktop (please complete the following information):

  • Ventura 13.5.2
  • VSCode 1.82.2 Universal

Additional context
More issues, if I try to use an interpolated string in a command block it looks like it doesn't get evaluated either which is unfortunate becausae I have an entrypoint.sh file that does some post up setup (the Docker image is fixed and can not be changed).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant