Chad Smith

Agreed on these restructuring points. I do think add some content on conventional commits docs in the first PR page would be a good refefence as the link in the...

big +1 on separating those docs for "power users" with custom downstream image needs and behaviors. These scopres are atypical for most cloud-init users.

the function `cloudinit.cmd.devel.read_cfg_paths` may be helpful in a lot of these cases for grabbing the configured run_dir from Paths.

Thanks @aciba90 and correct, I think this is something we should look to implement. The `cloud-init clean --logs` and `collect-logs` determine their related log files from merged configuration in [cloudinit.util.get_config_logfiles](https://github.com/canonical/cloud-init/blob/main/cloudinit/util.py#L1739)....

> > Affects cloud-init [21b2b6e](https://github.com/canonical/cloud-init/commit/21b2b6e4423b0fec325b32042c05ef4274cdd301) and earlier > > @blackboxsw are you saying that this was introduced in the dhcpcd PR? That is surprising, since that PR doesn't touch any...

Thanks @adrien-n for the update and reproducer steps here. I think something like the following is what we want in this case. we want to force apt update to run...

Confirmed a slightly difference error/warning on cloud-init 24.1~1g1003d438 on Ubuntu Noble. We should sort non-root use of schema validation for files that do not require root read-only permission. ``` ubuntu@nnn:~$...

Hi @paul-pascual thank you for filing this bug and making cloud-init better. I think we may need a few more details here to understand the use-case you are trying to...

cc: @Meulengracht for snap-related concerns.

> Because we patched out the `exit 2` behavior on old releases, there's no backwards incompatibility here, correct? Just an extra warning in the logs? > > We would see...