S3 single bucket to local with PostgreSQL + SSE-C encryption #22
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This is the original s3tolocal.php, adapted to PostgreSQL with additionally handling SSE-C encrypted objects.
The queries are exactly the same, just adapted for Postgres operation.
The S3
getObjectconfiguration system is a bit different, it uses the same$optsarray for every call, only changing theKeyandSaveAsvalues.If SSE-C is configured in
config.php, the required parameters are added to thegetObjectcall.Tested with a small test server running Nextcloud 31.0.9 with PHP-FPM.