feat: pgbouncer health check #183
Merged
Conversation
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
hrodmn
changed the title
jjfrench
approved these changes
Sep 15, 2025
Contributor
jjfrench
left a comment
jjfrench
left a comment
There was a problem hiding this comment.
Overall, I think that it looks good
github-actions bot
pushed a commit
that referenced
this pull request
Sep 15, 2025
# [10.2.0](v10.1.1...v10.2.0) (2025-09-15) ### Features * pgbouncer health check ([#183](#183)) ([d560291](d560291))
Contributor
|
🎉 This PR is included in version 10.2.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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.
Merge request description
I was having some trouble with the pgbouncer startup script failing in a deployment due to a dpkg lock so I added some additional logic to the
wait_for_dpkg_lockfunction. While I was at it I thought it would make sense to optimize the unattended-upgrades setup since these instances might stay running for a long time. I also added a health check Lambda function to make sure that pgbouncer is correctly installed and running.The problem I encountered with pgbouncer caused a silent failure of all of the API services! To make sure we are at least testing database connectivity in our development in eoapi-cdk I added some health check requests to the deployed APIs in the integration test deployment in Github Actions.