fix(api): preserve existing database secrets - #43
Conversation
|
Warning Review limit reachedYou’ve reached a temporary PR review limit under our Fair Usage Limits Policy. Next review available in: 47 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?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 reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. 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, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
Comment |
Summary
api-db-secretwhendb.useExistingSecret=trueVerification
tests/unit/test-api-existing-secret.sh(passed: 10 references, no generated Secret)helm lint helm/charts/api --set db.useExistingSecret=true --set db.existingSecretName=api-db-secret(passed)Context
This unblocks the reproducible backend DevSpace lane needed for REL-255 without placing database credentials in source. It does not close tenant/appliance acceptance by itself.
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.