and machines can access some of the deployment information via the following options (set by NixOps): * deployment.name * deployment.uuid * deployment.arguments
This was leading to bad /etc/hosts entries, e.g. lucifer lucifer lucifer-unencrypted
This fixes the behaviour of ec2.associatePublicIpAddress which cannot safely be set to false when deploying inside a subnet before this commit. Add a new option ec2.usePrivateIpAddress which will default to true in the case that associatePublicIpAddress is false and you are deploying to a subnet. Add supporting code in the ec2 backend to support this option. This required storing some state from the defn in the machine state, but it seems that's already being done for other things like the spot instance price so this seems consistent.