Fix ssl.SSLError: [SSL: HTTP_REQUEST] http request (_ssl.c:997) in Sp… #909
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.
Hi Team,
I opened the following issue:
#889
that explain a problem I found on Spilo 3.0-p1 code. In September 2021 I submitted two PRs to add SSL support to Patroni:
#629
#625
however, I found out that the file
postgres-appliance/scripts/patroni_wait.sh
doesn't manage SSL variable so an error message appear at startup if patroni is configured in SSL (see my issue above). I had a discussion with Alexander Kukushkin on Slack and we agreed a possible solution. This solution, at the moment, is already running in my company dev, staging and production systems with an external patch I applied to Spilo 3.0-p1 during our build.However, I would like to have this fix in the official code.