diff options
| author | Scott Moser <smoser@ubuntu.com> | 2011-12-20 12:02:39 -0500 |
|---|---|---|
| committer | Scott Moser <smoser@ubuntu.com> | 2011-12-20 12:02:39 -0500 |
| commit | b17a271da699230be8dad5d8c0227a5c7c238503 (patch) | |
| tree | fc0f9419f83f8533cf6d6259b45c195795f4bb94 /debian.trunk/rules | |
| parent | 13015ef25fa7e748e916c99f083e338b28861a18 (diff) | |
| parent | 57a28850fae6098a32e7c16ab90541fd785684cb (diff) | |
| download | vyos-cloud-init-b17a271da699230be8dad5d8c0227a5c7c238503.tar.gz vyos-cloud-init-b17a271da699230be8dad5d8c0227a5c7c238503.zip | |
add INSTANCE_ID to env of bootcmd, add cloud-init-per
the environment varible INSTANCE_ID is set when invoking boothooks from
multi-part input. However, previously that was not the case for things
run via bootcmd.
This adds cloud-init-per, which makes it easy for user in bootcmd or
boothook to do something per 'instance', 'always', or 'once'.
The functionality in cloud-init-per mostly duplicated what was in
cloud-init-run-module. That supported "modules", but it is unlikely
that it was used for anything other than "execute". So, cloud-init-per
now replaces cloud-init-run-module and provides legacy support for
the 'execute' path.
Diffstat (limited to 'debian.trunk/rules')
| -rwxr-xr-x | debian.trunk/rules | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/debian.trunk/rules b/debian.trunk/rules index 200b7abb..95bff792 100755 --- a/debian.trunk/rules +++ b/debian.trunk/rules @@ -14,6 +14,7 @@ cloud-init-fixups: for x in $(DEB_DESTDIR)/usr/bin/*.py; do mv "$$x" "$${x%.py}"; done install -d $(DEB_DESTDIR)/etc/rsyslog.d cp tools/21-cloudinit.conf $(DEB_DESTDIR)/etc/rsyslog.d/21-cloudinit.conf + ln -sf cloud-init-per $(DEB_DESTDIR)/usr/bin/cloud-init-run-module # You only need to run this immediately after checking out the package from # revision control. |