added --no-progress to aws s3 commands to create sane log files.... #97
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.
added the date to the script output. Couldn't find the --no-progress documented anywhere official, but found it in Github aws/aws-cli#2747 and it works. Instead of 25 MB for one backup job, the log file is now a handful of bytes and we have just as much usable info. Also added some "echo" statements to log what point of the cleanup we are in for when one of those things fails (had some trouble with it in manual testing). This worked for a test run on testnet.