Changelog¶
1.0.0 (2021-08-23)¶
- Bump to 1.0.0 since I’ve been using this for years
- Build and test against Python 3.9; build Docker image off of Python 3.9
- Add
rsnapshotapk to Docker image - Updates for new pytest version
0.4.3 (2021-01-06)¶
- Fix deprecated PyYAML load calls.
0.4.2 (2021-01-06)¶
- Relax PyYAML version in order to work with Python 3.9.
0.4.1 (2018-08-11)¶
- Add leading newlines when passing report to
failure_command - In the
failure_html_pathglobal config setting, the string{date}will be replaced with the current datetime (at time of config load) in%Y-%m-%dT%H-%M-%Sformat.
0.4.0 (2018-02-25)¶
- Add
awsclito Docker image - Add new global configuration options:
- failure_html_path - (optional) a string absolute path to write the HTML email report to on disk, if sending via SES fails. If not specified, a temporary file will be used (via Python’s
tempfile.mkstemp) and its path included in the output. - failure_command - (optional) Array. A command to call if sending via SES fails. This should be an array beginning with the absolute path to the executable, suitable for passing to Python’s
subprocess.Popen(). The content of the HTML report will be passed to the process on STDIN.
- failure_html_path - (optional) a string absolute path to write the HTML email report to on disk, if sending via SES fails. If not specified, a temporary file will be used (via Python’s
0.3.0 (2017-12-01)¶
- Document release process
- Document how to run in ECS as a Scheduled Task
LocalCommand- ifscript_sourceparameter is specified, instead of ignoringcommandsend it as arguments to the downloaded script.LocalCommandbugfix - Handle when retrieved script_source is bytes instead of string.- Add
-m/--only-email-if-problemscommand line argument to allow suppressing email reports if all jobs ran successfully. - Make report email subject configurable via
email_subjectglobal configuration option.
0.2.0 (2017-11-30)¶
- Initial mostly-complete release