-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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 CLI requests have inaccurate user agent #11996
Comments
terrytangyuan
added a commit
to terrytangyuan/argo-workflows
that referenced
this issue
Nov 27, 2023
Signed-off-by: Yuan Tang <terrytangyuan@gmail.com>
terrytangyuan
added a commit
that referenced
this issue
Nov 27, 2023
sarabala1979
pushed a commit
that referenced
this issue
Jan 9, 2024
isubasinghe
pushed a commit
to isubasinghe/argo-workflows
that referenced
this issue
Mar 12, 2024
isubasinghe
pushed a commit
to isubasinghe/argo-workflows
that referenced
this issue
May 6, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Pre-requisites
:latest
What happened/what you expected to happen?
Currently, requests through Argo CLI have the user agent
argo/v0.0.0
. It should be more distinguishable likeargo-cli/v3.4.5
. These were missed when I initially added the user agents in #5624 and #5014.Version
latest
Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
Not necessary
Logs from the workflow controller
Logs from in your workflow's wait container
The text was updated successfully, but these errors were encountered: