chore: queue-service 다중 EC2 순차 배포 적용 - #19
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 (1)
✨ 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 |
📎 관련 이슈
📌 작업 내용
queue-serviceCD workflow의 배포 대상을 기존 단일 EC2에서 main-1, main-2 EC2 2대로 확장했습니다.ticketing-systemcompose 설정을 반영한 뒤queue-service컨테이너를 재생성하도록 구성했습니다.✨ 변경 사항
Deploy queue-service to main-1 EC2step 추가Deploy queue-service to main-2 EC2step 추가http://localhost:20007/actuator/health기반 health check 추가QUEUE_TOKEN_SECRET설정은 유지📝 리뷰 포인트 (선택)
EC2_HOST_2GitHub Actions Secret이 추가되어 있어야 정상 동작합니다.🧠 기타 참고 사항
EC2_HOST는 main-1 EC2를 의미합니다.EC2_HOST_2는 main-2 EC2를 의미합니다.queue-service버전을 실행하도록 배포 흐름을 정리했습니다.