Skip to content
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

Support context switch for argocd-util #5912

Open
galan opened this issue Mar 30, 2021 · 3 comments · May be fixed by #7538
Open

Support context switch for argocd-util #5912

galan opened this issue Mar 30, 2021 · 3 comments · May be fixed by #7538
Assignees
Labels
enhancement New feature or request good first issue Good for newcomers hacktoberfest

Comments

@galan
Copy link
Contributor

galan commented Mar 30, 2021

Summary

I have multiple contexts I need to switch between, it would be very helpful to switch the context on a global level via an argument or environment-variable.

Motivation

Let's assume you have three contexts named dev, staging and production and are constantly changing via argocd context dev...., argocd context staging.... or argocd context production...., prior actual execution of the desired action. Also you have to check each time which context you are currently working in prior execution.

So the current workflow is:

# check which context I'm in
argocd context
# switch if required
argocd context staging...
# execute command, eg:
argocd app list

Proposal

Pass the context in the actual command, eg:

argocd app list --context staging...

or as environment variable

ARGOCD_CONTEXT=staging... argocd app list
@galan galan added the enhancement New feature or request label Mar 30, 2021
@nekia
Copy link
Contributor

nekia commented Oct 19, 2021

I'd like to work on this issue if anyone hasn't done yet.

@nekia nekia linked a pull request Oct 24, 2021 that will close this issue
10 tasks
@crenshaw-dev crenshaw-dev assigned nekia and unassigned nekia Sep 20, 2023
@crenshaw-dev
Copy link
Collaborator

Looks like the PR just needs a review (and probably massive rebase).

@waddles
Copy link

waddles commented Sep 20, 2023

Looks like the PR just needs a review (and probably massive rebase).

It's a 1-line change with ~133 generated docs changes and it's already had a review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request good first issue Good for newcomers hacktoberfest
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants