feat: Trigger immediate ArgoCD refresh to speed up revision detection #213
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
FEATURE: Trigger immediate ArgoCD refresh when monitoring starts to significantly reduce revision detection time.
Problem
ArgoCD polls Git repositories on a periodic interval (typically 3 minutes by default). This means after pushing a manifest, it can take 30+ seconds before ArgoCD detects the change and starts syncing.
Example from deployment logs:
Wait time: 36 seconds before ArgoCD detected the new revision
Solution
Trigger an immediate ArgoCD refresh at the start of monitoring using
argocd app get --refresh. This tells ArgoCD to check the Git repository right away instead of waiting for its next polling interval.Changes
wait-sync.sh
New refresh trigger before monitoring loop:
How It Works
argocd app get --refresh:|| true) - won't block monitoring if it errorsExpected Impact
Before:
After:
Total deployment time reduction: 20-170 seconds per deployment
Testing
After merge:
🤖 Generated with Claude Code