fix(ci): repair timed-out SST ACM certificate state#942
Conversation
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Summary
sst deployso the next deploy can create a fresh certificate after the earlier Cloudflare-token failureRoot Cause
The failing run at https://github.com/AgentWorkforce/relay/actions/runs/26252592498/job/77298304399 reused an ACM certificate that had already reached
VALIDATION_TIMED_OUT. The first failure in the series createdWebCdnSslCertificate, then failed during Cloudflare zone lookup because the token was invalid, leaving SST state with a cert that never validated.Validation
bash -n .github/scripts/repair-failed-sst-acm-cert.shshellcheck .github/scripts/repair-failed-sst-acm-cert.shactionlint .github/workflows/deploy-web.yml.github/workflows/deploy-web.yml