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

Feature request: ArgoCD dry run #160

Open
sthomson-wyn opened this issue Mar 15, 2024 · 2 comments
Open

Feature request: ArgoCD dry run #160

sthomson-wyn opened this issue Mar 15, 2024 · 2 comments
Labels
enhancement New feature or request

Comments

@sthomson-wyn
Copy link

It would be neat if kubechecks ran a dry sync with the argocd CLI.

https://argo-cd.readthedocs.io/en/stable/user-guide/commands/argocd_app_sync/

Flags of interest:
--dry-run
--local
--server-side

If this works how I think it does, this would allow users to identify things like validating webhook violations at PR time, rather than deploy time

@djeebus
Copy link
Collaborator

djeebus commented Mar 18, 2024

Very interesting, I like the idea!

@djeebus djeebus added the enhancement New feature or request label Mar 28, 2024
@MeNsaaH
Copy link
Collaborator

MeNsaaH commented Feb 4, 2025

Yeah, I stumbled unto this when I was searching for how to validating webhook. I remember bumping into an issue that delayed my progress:

  1. It doesn't work for new resources, see Improve argocd app sync --dry-run for Applications with New Resources argoproj/argo-cd#21660
  2. It sorta modifies the actual application - I need to retest this and verify though. But I noticed this wild behaviour where argocd sync --dry-run updated the actual app, and in most cases left that app out-of-sync.

I'll hopefully be working on this feature soon

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

No branches or pull requests

3 participants