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
You see ENDPOINT is set with quotes within the environment variable itself. What I expected was this to be set to the content of the string, without quotes.
I now have to cleanup the environment variables before I can use them.
Is this a BUG REPORT or FEATURE REQUEST?: BUG REPORT
What happened: Environment variables from parameter file are encapsulated in quotes.
What you expected to happen: I expected the environment variable to be set to the correct value without adding quotes to the string.
How to reproduce it (as minimally and precisely as possible):
Given the following workflow:
with the following parameter file:
Invoked like this:
You see ENDPOINT is set with quotes within the environment variable itself. What I expected was this to be set to the content of the string, without quotes.
I now have to cleanup the environment variables before I can use them.
Note that integer values are correctly set.
Anything else we need to know?:
Environment:
PS: I'm otherwise super happy with Argo. It is a very useful tool for me and it sparks joy.
The text was updated successfully, but these errors were encountered: