Comment 5 for bug 1810859

On Tue, Apr 30, 2019 at 10:11 AM Scott Moser <email address hidden>
wrote:

>
> @Ryan,
> I don't think that "cloud-init as a daemon" actually solves the problem at
> all. cloud-init aims to provide structured points at boot when a user (or
> cloud-init) can operate. If running later later (after such a device shows
> up) then cloud-init is not providing that point in boot and thus failing in
> a different way.
>

You're right that it does not solve boot-time configuration if user-data is
present problem. I do think that transitioning to having the daemon that
reacts to events means that for some scenarios which don't need to run at
boot time only, will be able to run later.

> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1810859
>
> Title:
> ds-identify runs too early
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/cloud-init/+bug/1810859/+subscriptions
>