Harden Textract Civil ID expiry extraction#93
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: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
✨ 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 |
Related to #55
/claim #55
Scope
This is a narrow, non-overlapping Textract Civil ID expiry extractor hardening slice. It does not touch the Civil ID upload/remove S3 flow, S3 credential env-var PRs, IAM/bucket policy work, CloudTrail helpers, Xero/OneSignal/SQS/MediaConvert/SES/service-token slices, live AWS access, candidate data, or real credential values.
Summary
IdExpiryDateExtractorfail closed when Textract credentials or the S3 document bucket/region are missing.photos/prefix before calling AWS.Verification
php -lcould not be run here because PHP is not installed in this environment. The PHP changes are limited to the existing Textract component and one cron guard, and the regression script checks the security-sensitive behavior directly.Safety boundary
No AWS/IAM/S3 API calls, key rotation/deletion, bucket policy changes, candidate records, Civil ID images, private exports, or credential values were accessed or included.
Transparency: automation-assisted; I reviewed the diff and validation before submitting.