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
Additional context from my debugging: Seems like we are expanding the envvars twice, because the stack expander is already expanding the envvars and changes the $${envvar} to ${envvar}
@AgustinRamiroDiaz if i recall correctly, the stack expander using the nodes was introduced in order to parse correctly the multiline envs... from that persperctive, if escaped envs are not being correctly expanded,
@AdrianPedriza could we add a unit test to ExpandEnv with this inputs and expected output to trace if the format is correct? sorry i dont remember 100% how this was expanded
Describe the bug
when I try to escape the value of an environment variable as allowed by docker, the escaped value is not reflected in my deployment.
To Reproduce
Steps to reproduce the behavior:
(Using docker compose)
docker-compose up
docker exec <container-id> /usr/bin/env
) contains escaped value:(using okteto)
okteto deploy -f docker-compose.yml
Expected behavior
I expect a behavior similar to that of docker compose where the escaped variable is correctly added as env
The text was updated successfully, but these errors were encountered: