Prune Sebastien THOMAS

I cloned @crenshaw-dev PR to https://github.com/argoproj/argo-cd/pull/16653 and solved the e2e test.

Well, it turn out @crenshaw-dev patch was working afterall, and my own patch was missing something. What is happening is that somehow (how ?) the clone on the project in...

To replicate the bug: ``` k exec -ti svc/argocd-repo-server bash cd /tmp chmod u+r _argocd-repo/ cd _argocd-repo/ ls -la # remove one of the project's folder chmod 0700 4048ada3-ecd6-4320-86a3-ee2887a68167/ rm...

> Any easy workarround without changing the docker image? nope, unless you want to automate a `repo-server` restart + a `hard refresh` of all your apps... :) You can import...

@crenshaw-dev it seems some e2e tests are failing, but not on the patch (e2e namespace creation failure ?) I tested the patch for few weeks now and I also managed...

> @prune998 not sure what's up here... > > ``` > time="2024-01-03T14:27:11Z" level=error msg="`kustomize build ./testdata/guestbook_local` failed exit status 1: Error: must build at directory: not a valid directory: evalsymlink...

I made some debug, and when run manually using `argocd` commandline, like in `argocd app diff`, the `repoRoot` is `/`, and any relative file path, like `testdata/config-map` from the e2e...

turns out we need to set `--local-repo-root` to locate the path of the repo. Let's say that it was previously working by chance more than by design...

@crenshaw-dev I got it working by changing the defaults `--local-repo-root` of the `app diff` and `app sync` commands from `/` to `.`. This was already the default for the `manifests`...

@crenshaw-dev are we good for adding this to release 2.10 ? thx !