Changelog: Explicit init parameters and logging for the scrubber lambda #3309
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: Enterprise 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 |
…da (#3309) * Add tighter and explicit timeout to S3 Client acquisition * Add intermediary logs
This pull request introduces the new
docs-lambda-changelog-scrubberproject to the solution and enhances its logging and AWS client initialization. The most important changes are grouped below:Project and Solution Structure
docs-lambda-changelog-scrubberproject to the solution filedocs-builder.slnx, making it part of the build and deployment pipeline.AWS Client Initialization
Program.csto explicitly use environment variable credentials and region, with custom timeout and retry settings for improved reliability and configuration clarity.Logging Improvements
Program.csto trace key operations, including removing objects from the public bucket, scrubbing and copying files, fetching objects from the private bucket, performing the scrub pass, and uploading to the public bucket. [1] [2] [3] [4]