Open sereneshikari opened 2 months ago
One more observation...
After creating the app with argocd app create
and syncing it with argocd app sync
, I tried to set it using argocd app set
:
./argocd app set hello-world --helm-set-string serviceAccount.name=foo --loglevel debug
and I got:
FATA[0001] Source position should be specified and must be greater than 0 for applications with multiple sources
I was able to successfully set
this using an older version of the CLI (v2.7.17
as also used above).
The log about "multiple sources" even though this is a single-source Application
makes me wonder if this is related to #18120.
same behavior observed with v2.11.0 --helm-set-string flags are ignored not observed when using v2.10.9
Checklist:
argocd version
.Describe the bug
The current latest version of the ArgoCD CLI (
v2.11.0
) does not respect--helm-set-string
during app creation.To Reproduce
Create a Kubernetes cluster with
kind
(skip if you already have a cluster since this is not crucial for reproduction):Follow the official instructions to install the current latest version of ArgoCD (
v2.11.0
):Download the current latest version of ArgoCD CLI (
v2.11.0
) and login:Create a test application manifest and save it to
hello-world-app.yaml
:Create the app and configure the
ServiceAccount
name to befoo
using the--helm-set-string
option:Sync the app:
After the app has synced, observe that the
ServiceAccount
name is notfoo
:Output:
Expected behavior
--helm-set-string
should be respected during app creation and theServiceAccount
name should have beenfoo
.Repeating the same steps above but with a different version of the ArgoCD CLI (in my case, I tried
v2.7.17
) resolves the issue:Screenshots
Version
Logs
This seems to be an issue with the CLI binary rather than the server but please let me know which logs are helpful and I'll send them. Please note that running
argocd app create
with--loglevel debug
did not print anything extra.