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

Catalog/S3: Allow custom trust and key stores #9012

Merged
merged 3 commits into from
Jul 5, 2024

Conversation

snazy
Copy link
Member

@snazy snazy commented Jul 4, 2024

Part of #8834

dimas-b
dimas-b previously approved these changes Jul 4, 2024
snazy and others added 2 commits July 5, 2024 12:31
…es/s3/S3Config.java

Co-authored-by: Dmitri Bourlatchkov <[email protected]>
…es/s3/S3Config.java

Co-authored-by: Dmitri Bourlatchkov <[email protected]>
@snazy snazy merged commit 916d0e9 into projectnessie:main Jul 5, 2024
18 checks passed
@snazy snazy deleted the custom-s3-trust-key-stores branch July 5, 2024 12:44
* nessie.catalog.service.s3.trust-store.password} must be supplied as well when providing a
* custom trust store.
*
* <p>When running in k8s or Docker, the path is local within the pod/container and must be
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should I go ahead an implement support for this in the Helm chart?

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.

3 participants