You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the argocd CLI tool creates its config file in the home directory.
Use $XDG_CONFIG_HOME instead.
Motivation
Keep the home directory free from clutter.
Proposal
Support the XDG base directory standard.
Alternatively, introduce an environment variable (eg. ARGOCD_CONFIG_HOME) to allow users controlling the config file location without having to pass --config to every command. This would also be backward compatible.
The text was updated successfully, but these errors were encountered:
* feat: support XDG Base directory standard
Signed-off-by: Mark Sagi-Kazar <mark.sagikazar@gmail.com>
* chore: set XDG_CONFIG_HOME env var for docs generation
Signed-off-by: Mark Sagi-Kazar <mark.sagikazar@gmail.com>
* chore: regenerate cli docs
Signed-off-by: Mark Sagi-Kazar <mark.sagikazar@gmail.com>
Summary
Currently the argocd CLI tool creates its config file in the home directory.
Use
$XDG_CONFIG_HOME
instead.Motivation
Keep the home directory free from clutter.
Proposal
Support the XDG base directory standard.
Alternatively, introduce an environment variable (eg.
ARGOCD_CONFIG_HOME
) to allow users controlling the config file location without having to pass--config
to every command. This would also be backward compatible.The text was updated successfully, but these errors were encountered: