virtualbox: allow destroy if the VM is gone already
Change default value of deployment.storeKeysOnMachine to false. The previous default value is the less secure option, better to use the more secure option.
Remove evaluation from backup/backup-status, as it is unnecessary and harmfull (when eval fails).
Revert "Remove evaluation from backup/backup-status, as it is unnecessary and harmfull (when eval fails)."

This reverts commit 2a5697137ad54dc85e1f5bcaea5c8a2d6af75cad.
Gathering release notes for 1.2 release.
postHook -> shellHook
Prevent restore from failing when choosing to keep volume around.
Make show-physical --backup consistent for pvgrub and hvm instances.
Fix release date.
route53: match zones with less components in it

allows to match zone 'example.com.' for a hostname 'service.staging.example.com'
if there's no hosted zone called 'staging.example.com.'
Merge pull request #180 from proger/route53-hostedzone-submatch

route53: match zones with less components in it
Merge pull request #179 from proger/virtualbox-destroy-even-if-gone

virtualbox: allow destroy if the VM is gone already
More release notes.
backends: Check units with systemctl --no-legend.

If legend is enabled, the unit names are indented by two spaces in
systemd 212. But if used with --no-legend we not only get something that
resembles the old behaviour, we also can be sure that we don't match
anything in the legend and/or additional descriptions around the actual
content.

Signed-off-by: aszlig <aszlig@redmoonstudios.org>
Merge pull request #181 from aszlig/systemd-212-fix

backends: Check units with systemctl --no-legend.
Fix release date, today is the day...
Amazon EC2 r3 instances are HVM instances as well.
Allow traffic on port 80 of httpd example in manual.
Add work-around for weird DescribeKeyPairs behaviour in EC2.