search

datadryad / vagrant-dryad

Vagrant and Ansible config for building a (v1) Dryad VM
0 stars 4 forks source link

Allow separate settings for production vs test machines #81

Closed daisieh closed 6 years ago

daisieh commented 6 years ago

Allow several settings to be set based on whether or not the machine is a production machine. Also adds the instance name to Opsworks when registering.

(also updates some deprecated settings and ignores setup.retry files)

daisieh commented 6 years ago

Note: I've never found the Name tag in the Vagrantfile to actually set the Name tag in EC2, and it still doesn't seem to do it, even though now it definitely adds the name to the opsworks:instance tag.

ryscher commented 6 years ago

The machine name appears in EC2 until the opsworks script runs, then it disappears (same behavior as before). The machine is now correctly labeled within opsworks.

ryscher commented 6 years ago

otherwise, looks good

daisieh commented 6 years ago

I filed an issue (https://github.com/aws/aws-cli/issues/3166) with AWS about opsworks overwriting the EC2 tags, but in the meantime, it is easy enough to re-assign the name after opsworks does its thing.

ryscher commented 6 years ago

Looks good! Tested on new VM