argocd repository webhook manifest cache warming controls and metrics
Introduced 2026-08-04 · score 0.93
HOW TO USE IT
For large monorepos or plain YAML repositories where webhook cache warming adds overhead, disable warming per repository with `argocd repo edit` or globally through the `argocd-server` environment variable. Inspect webhook volume and cache reuse with the two documented metrics.
argocd repo edit https://github.com/<org>/<repo>.git --webhook-manifest-cache-warm-disabledARGOCD_WEBHOOK_MANIFEST_CACHE_WARM_DISABLED=trueWHY THIS HELPS
Reduce webhook processing overhead or inspect manifest-cache warming activity for a repository.
REQUIREMENTS AND LIMITATIONS
- Version: v3.5.0
- --webhook-manifest-cache-warm-disabled: Disables manifest cache warming for the repository being edited.
- repository URL (required): Repository URL passed to `argocd repo edit`.
- webhookManifestCacheWarmDisabled: Repository resource field; set to `true` to disable warming for that repository.
- ARGOCD_WEBHOOK_MANIFEST_CACHE_WARM_DISABLED: Set to `true` on argocd-server to disable warming for all repositories.
- argocd_webhook_requests_total: Counts incoming webhook events per repository; label: `repo`.
- argocd_webhook_store_cache_attempts_total: Counts attempts to reuse cached manifests for a new commit when refresh paths have not changed; labels: `repo`, `successful`.
- The global setting affects argocd-server.
- The per-repository setting disables warming for that repository.
- Cache warming can add overhead for large monorepos with many applications or plain YAML repositories where manifest generation is fast.
FIRST-PARTY EVIDENCE
- https://github.com/argoproj/argo-cd/releases/tag/v3.5.0
- https://github.com/argoproj/argo-cd/pull/27215
- https://argo-cd.readthedocs.io/en/release-3.5/operator-manual/high_availability/
Check the installed version and the source before using it. Entry JSON