ubuntu/mantic-23.4.x : lp:cloud-init : Git : Code : cloud-init

Get this branch:: git clone -b ubuntu/mantic-23.4.x https://git.launchpad.net/cloud-init

Members of cloud-init Commiters can upload to this branch. Log in for directions.

Branch merges

Branch information

Name:: ubuntu/mantic-23.4.x

Repository:: lp:cloud-init

Recent commits

b578c3f... by Chad Smith on 2024-02-27

releasing cloud-init version 23.4.4-0ubuntu0~23.10.1

57fc337... by Chad Smith on 2024-02-27

update changelog (new upstream snapshot)

3c61d28... by Brett Holman on 2024-02-27

Release 23.4.4

Bump the version in cloudinit/version.py to 23.4.4 and update ChangeLog.

8baa30d... by Brett Holman on 2024-02-23

fix(nocloud): smbios datasource definition

deprecate nocloud-net name

8d208fa... by Brett Holman on 2024-02-26

tests: Check that smbios seed works

- Verify that NoCloud smbios seed gets read for file://
- Verify that NoCloud smbios seed gets read from http:// and https://

0a9b3b5... by Gilbert Gilb's <email address hidden> on 2024-02-01

fix(source): fix argument boundaries when parsing cmdline (#4825)

When the command-line includes an argument that contains `ds=`, the rest
of the argument is always interpreted as a datasource, regardless of
wether the argument is `ds` or just the suffix of another argument.
While this doesn't cause issues in a majority of cases, it starts
conflicting with other arguments that also include `ds=` but do not
refer to a cloud-init datasource. For instance, setting
`bonding.max_bonds=0` in the command-line (which is a real-world
use-case) conflicts with the current implementation.

To fix this issue, this commit ensures that `ds`, `ci.ds` and
`ci.datasource` arguments are either at the very beginning of the
command-line, or just before a whitespace, so that we don't match
another argument.

bc7e354... by James Falcon on 2024-02-02