Daniel Rodgers-Pryor 8a9753032c Allow EC2 fleet packer instances to run in parallel ...

Without conflicting over the name of the launch template that they create/delete.

Previously, the launch template name was just hard coded to `packer-fleet-launch-template`, but since AWS enforces unique template names within an account, this caused simultaneously running packer instances to hit template-already-exists errors when creating their templates and race-conditions around deleting the template. Now, the template name is randomly generated on each run, so there should be no conflicts.

2019-06-30 16:19:35 +10:00

..

chroot

fix typos

2019-05-07 16:44:29 -07:00

common

Allow EC2 fleet packer instances to run in parallel

2019-06-30 16:19:35 +10:00

ebs

add skip_save_build_region flag to fix naming conflicts when building for multiple regions

2019-06-17 14:39:11 -07:00

ebssurrogate

refactoring step_run_spot_instance and swapping out the calls to create a spot instance with a call to create a spot fleet of one, so that we can be more flexible with the instance type when desired

2019-05-24 09:32:54 -07:00

ebsvolume

refactoring step_run_spot_instance and swapping out the calls to create a spot instance with a call to create a spot fleet of one, so that we can be more flexible with the instance type when desired

2019-05-24 09:32:54 -07:00

instance

refactoring step_run_spot_instance and swapping out the calls to create a spot instance with a call to create a spot fleet of one, so that we can be more flexible with the instance type when desired

2019-05-24 09:32:54 -07:00