Open shamil opened 1 year ago
This would be really useful for us. We have a bunch of documentation with a scattering of # point your kubectl context to the right cluster
comments, and it'd be so much easier to have --kube-context
work as expected.
I don't know if this flag is intended for a different purpose, but having it be a global flag does make me expect it to work as described by the issue.
Big 👍🏻 !!
+1 for this bug fix. We have lots of clusters and scripts to manage them. This flag will ensure that scripts (using argocd cli) runs on correct clusters
Checklist:
argocd version
.Describe the bug
I want to override
current-context
by using the--kube-context
flag. But seems likeargocd
cli ignores it.To Reproduce
The following command fails:
also even when I login with
--core
I get the follwoing error
When I change the
current-context
, everything worksExpected behavior
argocd
cli should not ignore the--kube-context
cli arg and properly overridecurrent-context
Version