1
# cloud-init normally emits a "cloud-config" upstart event to inform third
2
# parties that cloud-config is available, which does us no good when we're
3
# using systemd. cloud-config.target serves as this synchronization point
4
# instead. Services that would "start on cloud-config" with upstart can
5
# instead use "After=cloud-config.target" and "Wants=cloud-config.target"
9
Description=Cloud-config availability
10
Wants=cloud-init-local.service cloud-init.service
11
After=cloud-init-local.service cloud-init.service