Bug#959486: cloud-init - Enable fallback data source if nothing is detected in ds-identify

[Bastian Blank <waldi@debian.org>]

Package: cloud-init
Version: 20.1-2
Severity: wishlist

cloud-init does some basic tasks, like
- network config (currently completely shadowed by our own),
- ssh host keys.

I think the most sensible setup would always enable cloud-init, and if
it only runs with the fallback datasource.

Currently we are using ds-identify.  This tools does not have any way to
only enable the fallback data source.

Any ideas?

Bastian

-- System Information:
Debian Release: bullseye/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 5.5.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8), LANGUAGE=en_GB:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages cloud-init depends on:
pn  cloud-guest-utils   <none>
ii  fdisk               2.34-0.1
ii  gdisk               1.0.5-1
ii  ifupdown            0.8.35+b1
ii  locales             2.30-4
ii  lsb-base            11.1.0
ii  lsb-release         11.1.0
ii  net-tools           1.60+git20180626.aebd88e-1
ii  procps              2:3.3.16-4
ii  python3             3.8.2-3
ii  python3-configobj   5.0.6-4
ii  python3-jinja2      2.10.1-2
pn  python3-jsonpatch   <none>
pn  python3-jsonschema  <none>
pn  python3-oauthlib    <none>
ii  python3-requests    2.23.0+dfsg-2
ii  python3-six         1.14.0-3
ii  python3-yaml        5.3.1-1+b1
ii  util-linux          2.34-0.1

Versions of packages cloud-init recommends:
pn  cloud-guest-utils  <none>
ii  eatmydata          105-7
ii  sudo               1.8.31p1-1

Versions of packages cloud-init suggests:
ii  btrfs-progs  5.6-1
ii  e2fsprogs    1.45.6-1
ii  xfsprogs     5.4.0-1+b1