Allowing zero-like values as env variables #390
Unanswered
bryan-garcia
asked this question in
Q&A
Replies: 2 comments 2 replies
-
Hi @bryan-garcia -- So this looks like it was a bug. Were you thinking of anything other than having zero value numerical values in the environment block? Are there other use cases you were thinking of? If it was just the bug, I can close this conversation since it's a duplicate of #391 and is fixed by #393 (if this was solely a bug). |
Beta Was this translation helpful? Give feedback.
2 replies
-
Handled by #393 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi Everyone,
There is an issue when providing integer 0 or float 0 in the env.variables block that triggers a ValueError being raised. Specifically it's in yamlspecification.py (method _verify_variables on line 190):
A value of integer/float 0 in the env.variables block clearly triggers this error.
Sometimes I don't want to use the global.parameter block to define my values, and simply want an env variable. What are some thoughts for allowing this from a design perspective?
Beta Was this translation helpful? Give feedback.
All reactions