-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ARGO_LOG_LEVEL
has no effect
#41
Comments
WFM? Can you try this: apiVersion: kit/v1
kind: Tasks
metadata:
name: kit
spec:
semaphores:
two: 2
tasks:
- name: test
command: sh -c "echo FOO=$FOO"
env:
- FOO=bar CI=1 kit test You should see:
|
yes, I see something similar at least:
|
if it works for you and not for me, maybe I'm on an old version? |
It could be something subtle going on, e.g. typo in name? Try a newer version and see if you can repro in a Codespace. |
confirmed it is newest version I'm running:
What are you running from argo-workflows directory? |
Please correct me where my process could be wrong:
|
It seems like the only way this can work is if the workflow-controller actually reads the environment variable $ARGO_LOG_LEVEL, which I don't think it does. Rather, I believe it can take the "--loglevel" as a command line argument. So, does that imply that the command listed in tasks.yaml should have all of those command line arguments passed in? e.g. |
seems to be that you need to use "ARGO_LOGLEVEL" rather than "ARGO_LOG_LEVEL", but the latter is what's used in workflows |
So, not an issue? |
An issue with Argo Workflows repo |
Also confirmed myself that the flag is Thank you both for debugging! |
Raised PR to fix this in Workflows: argoproj/argo-workflows#11978 Can confirm that it is working there after the fix. Though I found another issue in Workflows that the Server currently ignores the env var for loglevel as well 😅 (similarly not a Kit issue though) |
If I set:
in argo-workflows' tasks.yaml file, it seems to have no effect. (I haven't tried the other environment variables.)
The text was updated successfully, but these errors were encountered: