cloudinit/extra/systemd/user-cloudinit@.service

[Unit]
Description=Load cloud-config from %f
Requires=coreos-setup-environment.service
After=coreos-setup-environment.service
Before=user-config.target
ConditionFileNotEmpty=%f

[Service]
Type=oneshot
RemainAfterExit=yes
EnvironmentFile=-/etc/environment
ExecStart=/usr/bin/coreos-cloudinit --from-file=%f
feat(units): Generic config drive and other systemd units. 2014-04-04 02:50:49 +04:00			`[Unit]`
			`Description=Load cloud-config from %f`
fix(units): Relax ordering requirements for now. The current cloudinit implementation blocks when starting units which causes it to deadlock the boot process if a system cloud config starts a user cloud config because the user configs want to run after system is done. Until cloudinit switches to non-blocking calls user configs will go back to just depending on coreos-setup-environment.service. 2014-04-15 05:38:38 +04:00			`Requires=coreos-setup-environment.service`
			`After=coreos-setup-environment.service`
feat(units): Generic config drive and other systemd units. 2014-04-04 02:50:49 +04:00			`Before=user-config.target`
			`ConditionFileNotEmpty=%f`

			`[Service]`
			`Type=oneshot`
			`RemainAfterExit=yes`
			`EnvironmentFile=-/etc/environment`
			`ExecStart=/usr/bin/coreos-cloudinit --from-file=%f`