Boto3 for just tablesnap, tokens and KMS encryption #89
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.
Hi guys,
Just thought I would put up another PR this time. This PR was born out of my need to able to use KMS to encrypt backups instead of just SSE but it doesn't look like I am able to do that using boto. So I bumped it to boto3 for just tablesnap only. Boto and boto3 can coexist during the migration so I figured this would be a start: http://boto3.readthedocs.io/en/latest/guide/migration.html
Functionally I've tested md5-on-start (just to be sure etags are right with multiparts...it may not have worked before..?), KMS, SSE, and generating tokens and of course, taking the backup. Let me know if there are any questions/issues/suggestions!
Thanks.