[FIX] discord secret 파일 권한 수정 - #154
Conversation
|
Warning Review limit reached
More reviews will be available in 47 minutes and 56 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
Walkthrough
Changesalertmanager 시크릿 마운트 권한 설정
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Poem
🚥 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. Comment |
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@infra/monitoring/docker-compose.yml`:
- Around line 25-29: The mode: 0444 setting on line 29 of the
discord_webhook_url secret mount is ineffective in non-Swarm Docker Compose
environments and will not solve the permission issue preventing the nobody user
in alertmanager from reading the secret file. Remove the ineffective mode
directive from the secret configuration and instead fix the root cause by either
setting appropriate file permissions (644 or 444) when creating the secret file
in the CI workflow (.github/workflows/ci-cd.yml), or by modifying the
alertmanager container setup to handle the permission issue through an
entrypoint script that changes ownership or runs the service with appropriate
privileges.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 5bcfeb53-1726-4ada-bc1d-32c6da2ce5ec
📒 Files selected for processing (1)
infra/monitoring/docker-compose.yml
This reverts commit 5fd8030.
Closes #152
Summary
ObritDown alert가 firing 상태에 들어가도 Discord 알림이 가지 않음
-> Alertmanager가 secret 파일을 권한 부족으로 읽지 못함
Changes
discord_webhook_url 파일 권한 변경
Etc
Summary by CodeRabbit
Chores