Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add SSE-C support to S3 Backend #54

Closed
wants to merge 3 commits into from
Closed

Add SSE-C support to S3 Backend #54

wants to merge 3 commits into from

Conversation

udf2457
Copy link
Contributor

@udf2457 udf2457 commented Sep 29, 2023

Re #52 : Update S3 backend to provide SSE-C support

SSE-C:
Disabled by default (empty key string), provide hex string to enable it.

(Previous NATS backend was breaking the CI, but I've now cherry-picekd that out. So SSE-C now works with old go.mod and CI now passes )

Update S3 backend to provide SSE-C support
@udf2457 udf2457 changed the title Add SSE-C support to S3 Backend Add SSE-C support to S3 Backend, Add initial NATS support Sep 29, 2023
@udf2457 udf2457 mentioned this pull request Sep 29, 2023
Add `Cluster` and `tag` placement hint support

Add NATS backend

Add NATS backend support.

Uses NATS JetStream Object Store (https://docs.nats.io/nats-concepts/jetstream/obj_store).

Code loosely based on the S3 backend.  Main difference is `use_update_marker` has not been implemented.

Update nats.go

Forgot to change name s3 to nats !

Add missing prefix test to List()

Original implementation of List() was not testing prefix.
This reverts commit 0ba9001.
@udf2457 udf2457 changed the title Add SSE-C support to S3 Backend, Add initial NATS support Add SSE-C support to S3 Backend Sep 29, 2023
@udf2457 udf2457 mentioned this pull request Sep 28, 2023
@udf2457 udf2457 closed this by deleting the head repository Oct 3, 2023
@udf2457 udf2457 mentioned this pull request Oct 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant