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
Hi,
I've done research, read through multiple issues touching default vars/overrides/env vars (I think the closest to my problem is this comment #181 (comment)) but I am still confused about best practices.
My requirements:
I want to use vars/go templating instead of relying on env vars, so that I can see the command fully on execution, I'd refer to env vars for something that is relevant to my application/script and not task itself (e.g. secrets)
I want to define vars explicitly, so that users can quickly see what they can/should provide
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
I've done research, read through multiple issues touching default vars/overrides/env vars (I think the closest to my problem is this comment #181 (comment)) but I am still confused about best practices.
My requirements:
Here is an example of Taskfile:
ID=456 task test
doesn't produce result I expect (overriden variable), unless I do:but it is cumbersome. At least it works.
For 4 I am using preconditions like this:
but it also feels a little weird.
Any recommendations/best practices?
Beta Was this translation helpful? Give feedback.
All reactions