Mercurial > hg
diff hgext/eol.py @ 43234:c09e8ac3f61f
automation: schedule an EC2Launch run on next boot
Without this, launching EC2 instances constructed from the AMI
won't go through the normal EC2 instance launch machinery. This
missing machinery does important things like set up network
routes to use the instance metadata service and process any
UserData.
Since EC2Launch now runs on subsequent boots and UserData is
processed, we needed to make setting of UserData conditional
on bootstrapping mode.
Differential Revision: https://phab.mercurial-scm.org/D7113
author | Gregory Szorc <gregory.szorc@gmail.com> |
---|---|
date | Mon, 14 Oct 2019 21:21:58 -0700 |
parents | 4aa9f3a1c1df |
children | 9d2b2df2c2ba |