Update postgres packaging #2632
Open
+2
−2
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
This is needed to get ssl support for pg_dump and pg_restore
cf-foundation-community-automation
bot
moved this to Inbox
in Foundational Infrastructure Working Group
rkoster
requested review from
a team,
benjaminguttmann-avtq and
ramonskie
and removed request for
a team
|
Why are you not using the https://github.com/cloudfoundry/backup-and-restore-sdk-release/blob/main/packages/database-backup-restorer-postgres-15/packaging package? |
rkoster
moved this from Inbox
to Pending Review | Discussion
in Foundational Infrastructure Working Group
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
What is this change about?
This is needed to get ssl support for pg_dump and pg_restore to dump and restore to external dbs using encrypted connections.
Please provide contextual information.
See also:
What tests have you run against this PR?
How should this change be described in bosh release notes?
Something brief that conveys the change and is written with the Operator audience in mind.
See previous release notes for examples.
Does this PR introduce a breaking change?
No
Tag your pair, your PM, and/or team!
@fmoehler