Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Request] - support encrypt files before pushing to object store

Open
#911 3 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
go
Domain
cloud, security

Research direction

Start with the EncryptionType API and internal/cnpgi/common/wal.go at the linked archiver call. Trace how WAL files are handed to the archiver and how encryption options reach the object-store API; done requires a defined symmetric-encryption configuration and verified protection before upload.

Written by the indexing model from the issue text.

Description

enhancement

As best as I can tell, the only options for tuning encryption are 'passed through' to the underlying s3 (or compatible) API calls.

If it turns out that I'm wrong on that one, please let me know!

My question/request: allow use of symmetric encryption before the files leave the host and are sent off to the object store.

I think this could be as straight forward as passing in a key/cypher to the underlying archiver

The motivation: not all object stores support "BYO" key for bucket encryption and even if they do, you're still required to hand the sensitive key material off to the remote backend so that it can encrypt things for you. One of the simplest ways to address this is to encrypt objects before they're ever off the host.
Symmetric encryption is sufficient for "at rest, I need to know that I truly am the only person that can read it" needs.

Dominant language
Go
Stars
192
Forks
75
Avg merge
1d 7h
Merged PRs (30d)
17

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from cloudnative-pg/plugin-barman-cloud

All issues in cloudnative-pg/plugin-barman-cloud

Similar issues

More Go issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.