ArgoCD manifest refactoring as a use case of argocd-diff-preview

[rklonner]

In general, when doing ArgoCD applicationset "development" I have 2 problems:

• during initial development I do not see which applications are created by what I write. Afaik argocd appset create --dryrun is only listing names of the applications, but not the rendered yaml. What I am basically looking for is the argocd cli equivalent of kubectl run nginx --image=nginx --dry-run=client -o yaml
• maintaining an application set is hard, when you modify refactor it to see the affect, e.g. moving from an initial list generator to a git generator

ArgoCD Diff Preview would allow for that when checking out the main and feature branch of the ArgoCD manifest repo and leaving the base and target branch for the k8s manifests "constant" at main (or just leave the default if argo and k8s manifests are in the same repo)

If you also think that makes sense and would be worth mentioning as an ArgoCD Diff Preview Use Case I can create an example.

[dag-andersen]

Hi @rklonner :)
Where would you add this "use-case" section in the docs? Would that be a new menu-item maybe, where we start listen use cases?

Nevermind you answered that in #266