From 03804622f0fa6963ddfe9fa9292b28653665365a Mon Sep 17 00:00:00 2001 From: Scott Moser Date: Fri, 17 Jun 2011 11:03:49 -0400 Subject: make the "cloud-config ready" command configurable (LP: #785551) Previously, when cloud-config was ready, cloud-init would emit an upstart event with: initctl emit cloud-config Now, that command is configurable via the 'cc_ready_cmd' value in cloud.cfg or user data. The default behavior is not changed. LP: #785551 --- doc/examples/cloud-config.txt | 12 ++++++++++++ 1 file changed, 12 insertions(+) (limited to 'doc') diff --git a/doc/examples/cloud-config.txt b/doc/examples/cloud-config.txt index b72cab48..eaedabeb 100644 --- a/doc/examples/cloud-config.txt +++ b/doc/examples/cloud-config.txt @@ -422,3 +422,15 @@ manual_cache_clean: False # on a per-always basis (to account for ebs stop/start), then set # manage_etc_hosts to True. The default is 'False' manage_etc_hosts: False + +# When cloud-init is finished running including having run +# cloud_init_modules, then it will run this command. The default +# is to emit an upstart signal as shown below. If the value is a +# list, it will be passed to Popen. If it is a string, it will be +# invoked through 'sh -c'. +# +# default value: +# cc_ready_cmd: [ initctl, emit, cloud-config, CLOUD_CFG=/var/lib/instance//cloud-config.txt ] +# example: +# cc_ready_cmd: [ sh, -c, 'echo HI MOM > /tmp/file' ] + -- cgit v1.2.3