feat: support default credential chain for AWS Secrets Manager#182
feat: support default credential chain for AWS Secrets Manager#182yoonhyunwoo wants to merge 1 commit into
Conversation
|
Warning Rate limit exceeded
To keep reviews running without waiting, you can enable usage-based add-on for your organization. This allows additional reviews beyond the hourly cap. Account admins can enable it under billing. ⌛ 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 (1)
📝 WalkthroughWalkthroughThe AWS Secrets Manager plugin makes Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ 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. Review rate limit: 0/1 reviews remaining, refill in 46 minutes and 10 seconds.Comment |
5555c19 to
10391e1
Compare
|
The test failure is not caused by this change Related: |
8381e38 to
09a289e
Compare
09a289e to
665bb2f
Compare
|
Rebased onto latest devel |
Make the access key and secret key optional to support default credentials (e.g., pod identity)
are used without exposing keys.
Also, ensure that if only one of the two is provided,
the operation fails naturally. Fallbacks to default behavior may confuse users.
Summary by CodeRabbit