Enhances the api to allow creation of alias records where the target
could be in a different hosted zone and also supports setting the target
health check flag on the alias record.
The different hosted zone is quite common if we are creating an alias to
an Amazon Load Balancer.
Also, without the health check flag being set, the AWS api will throw an
exception when creating an alias to an ELB.
Finally, when creating an alias record, the api was failing because an
empty ResourceRecord was being passed to the create request.

The hosted zone id of the alias target is different from that of the
hosted zone from which the record is being removed. Using the hosted
zone id of the zone from which the record is being deleted is not
correct.

…ous ASG is

Apparently there is a limit of 400 ELBs per request, and we need to start using the "optional" marker to get the rest.

Similar to a properties file.

…to ones that have a purpose.

This allows Asgard for certain AWS accounts to use properties file formatted user data for all windows AMI deployments, without changing the behavior of Asgard managing other AWS accounts.

…lication from a single source account.

The old code assumed that there could only be a single target account for image replication.

because last() throws an exception for an empty Collection

In order to support automatically taking any block device mapping of an AMI into an ASG they can be taken from the image itself. Any default EBS volumes on the AMI will be mounted as usual. 

This solves the issue we've been having with asgard not mounting the ephemeral disks in the AMI

Gives presedence for those in the configuration

This reverts commit ff6e5e1, reversing
changes made to d527213.

…us ASG.

We do not want to disable the whole ASG.