fix: respect PostgreSQL port in database connection#123
Merged
Conversation
Contributor
WalkthroughThe Helm chart now renders PostgreSQL host and port together in ChangesPostgreSQL connection environment variables
Estimated code review effort: 2 (Simple) | ~10 minutes 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 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 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
postgresql.portinDATABASE_HOSTwhen constructing the database connectionDATABASE_PORTenvironment variableTesting
helm unittest charts/sourcebot --colorhelm lint charts/sourcebot -f charts/sourcebot/values.lint.yamlgit diff --checkSOU-1524
Closes #122
Note
Medium Risk
Changes deployment-time database connection env vars; misconfiguration could break DB connectivity on upgrade, though behavior aligns with how the app expects the host string.
Overview
Fixes Helm-generated database env so non-default PostgreSQL ports actually reach the app.
DATABASE_HOSTis now built via a newsourcebot.postgresql.addresshelper: hostname pluspostgresql.port, unless the host value already includes a port (including bracketed IPv6). The separateDATABASE_PORTenv var is removed because entrypoint/DATABASE_URLassembly only used host.Adds helm unittest cases for bundled Postgres, external host + custom port, and host strings that already contain a port.
Reviewed by Cursor Bugbot for commit 82ea812. Bugbot is set up for automated code reviews on this repo. Configure here.
Summary by CodeRabbit