ops / backup-file2s3 · Files

0.4.1 - 2017-01-04

Fixed

• Bug where backup script uploads an additional, unneeded copy if bak_maxcopies is set to 1.

0.4.0 - 2016-12-13

Added

• AWS bucket and region can now be specified per element of the attribute node['backup-file2s3']['backups']. If not specified, bucket and region will default to the global node attributes node['backup-file2s3']['bucket'] and node['backup-file2s3']['region'], respectively.

Fixed

• Fixed a logic bug when trying to determine if at least one enabled path specification is encrypted or not.

0.3.3 - 2016-11-29

Fixed

• A typo in the backup script (missing end quotes).

0.3.2 - 2016-11-29

Fixed

• Reverted previous fix: paramter 'creates' for 'aws_tar_extract' should be mandatory.

0.3.1 - 2016-11-28 [YANKED]

Fixed

• Fixed definition for 'aws_tar_extract' where it raises an exception if no 'creates' parameter is given.

0.3.0 - 2016-11-25

Changed

• 'dirs' attribute has been replaced with 'backups' which gives the option of creating multiple instances of the script, each having a different filename.
• Maximum number of backup copies can now be specified for each file/directory to be backed up.
• Attributes for cron entries have been simplified.
• Definition for 'aws_tar_extract' now includes options for decrypting encrypted tarballs. The contents of the private key file must be provided in this case.

Added

• An option whether or not to use encryption for each file/directory backup is provided. If encryption is used, proper encryption keys must be provided beforehand as node attributes.
• Backup copies stored in S3 are now stored in their own subfolders (prefixes) along with a text file indicating the timestamp for when that backup was originally uploaded.

0.2.1

• Include tar cookbook in default recipe.

0.2.0

• Add definition aws_tar_extract to abstract reloading of backups.

0.1.0

• Initial release of backup-file2s3