Add age encryption support for database backups #70
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.
Summary
Adds support for age encryption to encrypt Litestream database backups at rest. This introduces two new configuration options:
age_recipient(public key) andage_secret_key(identity/private key).Changes
Core Configuration
age_recipientandage_secret_keytoLitestream::ConfigurationLITESTREAM_AGE_RECIPIENTandLITESTREAM_AGE_SECRET_KEYare now set in thepreparemethod for all commandsRake Tasks
litestream:envtask to output the new age encryption variablesGenerator Templates
age:section withrecipients:andidentities:fields following the Litestream age encryption formatTesting
age_recipientandage_secret_keyfor all commands (replicate, restore, databases, generations, snapshots, wal)litestream:envtask test expectationsUsage
Users can configure age encryption in their
config/initializers/litestream.rb: