fix(#466,#467,#468): fix Kubernetes cluster creation#489
fix(#466,#467,#468): fix Kubernetes cluster creation#489
Conversation
|
Warning Rate limit exceeded
To continue reviewing without waiting, purchase usage credits 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 (7)
✨ 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 |
77bd93d to
91d38ed
Compare
Summary
Fix three blocking issues that prevent Kubernetes cluster creation:
Changes
internal/workers/cluster_worker.go: Set TenantID in context alongside UserIDinternal/repositories/postgres/cluster_repo.go: Added tenant_id to INSERT, GetByID, ListByUserID, Update, Delete, ListAll, and scanClusterinternal/repositories/postgres/migrations/100_add_clusters_tenant_id.up.sql: Migration to add tenant_id columnDockerfile: Copy k8s templates to production imagedocker-compose.yml: Add CLOUD_API_URL env var.env.example: Document CLOUD_API_URLTest Plan
Related Issues
Fixes #466, #467, #468