pshima/consul-snapshot

KMS Crypto for backups is a no-op.

Closed this issue · 1 comments

Specifying CONSUL_SNAPSHOT_S3_SSE and CONSUL_SNAPSHOT_S3_SSE_KMS_KEY_ID does not encrypt backups. Looking at the code these env variables are stored in Go variables at startup but never referenced again.

This is working as expected.