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:
Create a .env file with OKTETO_NAMESPACE=foobar
Create an okteto 2.0 manitest and use the namespace: "${OKTETO_NAMESPACE}
Try to do an env up or down via vscode (okteto up and okteto down work on the command line)
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).
Describe the bug I have defined a
.envfile withname=valuepairs that should be interpolated beforeup,down, operations. They work underoktetoCLI but not through the vscode extension.To Reproduce Steps to reproduce the behavior:
.envfile withOKTETO_NAMESPACE=foobarnamespace: "${OKTETO_NAMESPACE}upordownvia vscode (okteto upandokteto downwork on the command line)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):
Additional context More issues, if I try to use an interpolated string in a
commandblock it looks like it doesn't get evaluated either which is unfortunate becausae I have anentrypoint.shfile that does some postupsetup (the Docker image is fixed and can not be changed).