Erich Blume
7d94b9073a
Now that argocd's Authentik OAuth2 client is public, `argocd login --sso` works for day-to-day use. Promote it to the default in AGENTS.md, argocd-cli reference, and troubleshooting; keep the admin/password flow documented as a break-glass fallback for when Authentik is unavailable. Also drops --grpc-web from every interactive login command — confirmed extraneous (login succeeds without it). Left in CI workflows and `argocd cluster add` untouched; those are different contexts that I didn't re-test. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
1.4 KiB
1.4 KiB
| title | modified | last-reviewed | tags | |||
|---|---|---|---|---|---|---|
| ArgoCD CLI | 2026-02-12 | 2026-04-01 |
|
ArgoCD CLI
Command-line workflows for deploying and managing applications via argocd.
CLI Commands
argocd app list # List all applications and sync status
argocd app get <app> # Show app details, health, and resources
argocd app diff <app> # Preview what would change on sync
argocd app sync <app> # Apply pending changes
argocd app sync apps # Sync the app-of-apps (picks up new Application manifests)
Login
Default (Authentik SSO, PKCE, opens browser):
argocd login argocd.ops.eblu.me --sso
Break-glass admin login (only if Authentik is down):
argocd login argocd.ops.eblu.me \
--username admin \
--password "$(op read 'op://vg6xf6vvfmoh5hqjjhlhbeoaie/srogeebssulhtb6tnqd7ls6qey/password')"
Branch-Testing Workflow
Test changes from a feature branch before merging:
# 1. Point the app at your branch
argocd app set <service> --revision <branch>
# 2. Sync to deploy the branch version
argocd app sync <service>
# 3. Test the changes...
# 4. After merge, reset to main and sync
argocd app set <service> --revision main
argocd app sync <service>