docs: add note on repo cache for git generator
Checklist:
- [x] Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
- [x] The title of the PR states what changed and the related issues number (used for the release note).
- [x] The title of the PR conforms to the Toolchain Guide
- [ ] I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
- [ ] I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
- [ ] Does this PR require documentation updates?
- [ ] I've updated documentation as required by this PR.
- [x] I have signed off all my commits as required by DCO
- [ ] I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
- [ ] My build is green (troubleshooting builds).
- [ ] My new feature complies with the feature status guidelines.
- [ ] I have added a brief description of why this PR is necessary and/or what this PR solves.
- [ ] Optional. My organization is added to USERS.md.
- [ ] Optional. For bug fixes, I've indicated what older releases this fix should be cherry-picked into (this may or may not happen depending on risk/complexity).
See these docs https://argo-cd.readthedocs.io/en/stable/operator-manual/high_availability/#argocd-repo-server
@todaywasawesome I'm using a pattern similar to what is described here: https://argo-cd.readthedocs.io/en/stable/operator-manual/applicationset/Generators-Git/#git-generator-files
When I add a new directory with a file similar to the config,json described in the example, the ApplicationSet is not picking it up after 3 minutes. Even restarting the applicationset controller and repo server does not trigger the creation of a new Application. Same with removal. When I reduce the caching for the repo server as described in this PR, the ApplicationSet picks up the new files. If this is considered a bug, I can file a Github issue for it.
@rolandkool would you mind sharing what version Argo CD you're using and what git provider?
I tested this with 2.10.7 iirc and the git provider is our internal gitlab instance.