diff options
| author | Pedro Alvarez <pedro.alvarez@codethink.co.uk> | 2014-09-23 11:03:16 +0000 |
|---|---|---|
| committer | Pedro Alvarez <pedro.alvarez@codethink.co.uk> | 2014-10-07 11:52:44 +0100 |
| commit | 48d79f276ca3b37e90a991e2e951d06d4e35c72b (patch) | |
| tree | ad0aa0ddf1b357b4e9f2296869ad283068349aff /busybox-init.configure | |
| parent | a8d42b546acbb827f0cba1243d2602f06125a10b (diff) | |
| download | definitions-48d79f276ca3b37e90a991e2e951d06d4e35c72b.tar.gz | |
Improve cloud-init.configure extension to detect cloud-init
Some users think that adding the cloud-init configuration
extension to a system is enough to install and enable cloud-init.
This is not true, to add and enable cloud-init in a system the
system has to have cloud-init installed (cloud-init chunk) and
cloud-init services have to be enabled (with cloud-init
configuration extension)
This patch is to alert the user that cloud-init can't be enabled
in a system without cloud-init installed, and making the
deployment fail.
Diffstat (limited to 'busybox-init.configure')
0 files changed, 0 insertions, 0 deletions