(mirror of https://github.com/vyos/vyos-cloud-init.git) https://git.amelek.net/vyos/vyos-cloud-init.git/atom?h=rolling 2020-09-17T11:06:18+00:00 2020-09-17T11:06:18+00:00 zsdc taras@vyos.io 2020-09-17T11:06:18+00:00 urn:sha1:e878af393dd99b45342dedc45d1dbf4cdb7b22a6 The startup order control was moved from the `cloud-config.service.tmpl` template to the `vyos-router.service` in the https://github.com/vyos/vyatta-cfg/commit/94f7abdf748c24b70c4741417c74147e52689da3 2018-10-25T20:26:25+00:00 Kim Hagen kim.sidney@gmail.com 2018-10-25T20:26:25+00:00 urn:sha1:b120f4f7a670674779a93f8c882c81f44a993888 Conflicts: cloudinit/sources/DataSourceAzure.py config/cloud.cfg.tmpl integration-requirements.txt tools/read-version 2018-10-21T19:30:24+00:00 Kim Hagen kim.sidney@gmail.com 2018-10-21T19:30:24+00:00 urn:sha1:46678295c78dac338111ec68c4bde2e005ef4491 2018-05-14T19:38:22+00:00 Scott Moser smoser@ubuntu.com 2018-05-14T19:38:22+00:00 urn:sha1:d5374bba2f1b4607a773ebff00e1ee7d66e23033 This makes cloud-config.service (and as a result cloud-final.service) run After snap.seeded.service. This is required to ensure that pre-seeded snaps can be used by cloud-init or user-data input. The snap.seeded.service was added to snapd at:   https://github.com/snapcore/snapd/pull/5124 Note that the following would be a workaround:  snap:   commands:    00: snap wait system seed.loaded LP: #1767131 2017-07-19T21:52:32+00:00 Ryan Harper ryan.harper@canonical.com 2017-06-13T14:06:41+00:00 urn:sha1:dcbe479575fac9f293c5c4089f4bcb46ab887206 Under el7, cloud-init systemd files need some unit tweaks to ensure they run at the right time. Pull in current el7 downstream systemd unit changes.