feat: Support context switch for argocd-util

[nekia]

Signed-off-by: Atsushi Neki nekiaiken@gmail.com

Note on DCO:

If the DCO action in the integration test fails, one or more of your commits are not signed off. Please click on the Details link next to the DCO action for instructions on how to resolve this.

Checklist:

• Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
• The title of the PR states what changed and the related issues number (used for the release note).
• I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
• I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
• Does this PR require documentation updates?
• I've updated documentation as required by this PR.
• Optional. My organization is added to USERS.md.
• I have signed off all my commits as required by DCO
• I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
• My build is green (troubleshooting builds).

Fixes #5912

[nekia]

I added context flag as follow:

And I've not added ARGOCD_CONTEXT yet because I'm not sure using environment variable manner has consistency with other flags. Should I work on it?

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 45.68%. Comparing base (4606476) to head (062f9b7).
Report is 2 commits behind head on master.

Files	Patch %	Lines
cmd/argocd/commands/root.go	0.00%	1 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #7538   +/-   ##
=======================================
  Coverage   45.67%   45.68%           
=======================================
  Files         353      353           
  Lines       46947    46952    +5     
=======================================
+ Hits        21445    21451    +6     
  Misses      22762    22762           
+ Partials     2740     2739    -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[wtam2018]

And I've not added ARGOCD_CONTEXT yet because I'm not sure using environment variable manner has consistency with other flags. Should I work on it?
I think just implementing it in the command fine. The strange thing is that I only see one line change in the root.go. Are there more changes to be pushed?

[nekia]

@wtam2018 Thank you for the review. No, there is no other than this one line change. In my understanding, basically Context in ClientOptions is expected that it's empty unless you explicitly specify other to use. The Context seems to be complemented by CurrentContext in config when calling ResolveContext.

[nekia]

I also noticed from one failure in CI that the newly added --context flag is conflicted with some other existing --context which come from kubectl flag (e.g. argocd admin settings --context [The name of the kubeconfig context to use]). Do we need to change the name of this new flag from --context to other one?

[nekia]

I changed the switch flag from --context to --argocd-context to avoid confusing with kubeconfig context flag , and merged files which were updated by running make clidocsgen.

[swerder-coop]

This simple and realy usefull change still not merged to the master branch, is there any reason for that?
The change #8849 for "--kube-context" made it to production in April 2022
But for use the argocd command on jenkins and allow parallel builds I need the --argocd-context from this issue.

my only workaround without this change is use --config and make different config files for each argocd context

[lionelnicolas]

Any update on this PR ?

[todaywasawesome]

@nekia I think this stalled primarily because there is a decent workaround with --config but I also still think this is relevant. If you want to fix the conflicts, I think we could get this one merged.

[todaywasawesome]

Lets just fix conflicts.

[todaywasawesome]

Ready to go

[pasha-codefresh]

LGTM, thank you!

[pasha-codefresh]

@nekia could you please do docsgen again ?

[kencochrane]

It looks like we still have one of the checks failing before we can merge. Anyone know how to fix it?