[01:57] <holman> cjp256 - Why override cmd? The disk shouldn't be formatted unless you explicitly list the disk (unless I'm misreading), so rather than overriding cmd why not just not list the ephemeral disk in the array under fs_setup?
[11:05] <cjp256> holman: for Azure, there is the BUILTIN_CLOUD_EPHEMERAL_DISK_CONFIG which is merged into the config with mergemanydict() https://github.com/canonical/cloud-init/blob/main/cloudinit/sources/DataSourceAzure.py#L750 which includes `"fs_setup": [{"filesystem": DEFAULT_FS, "device": "ephemeral0.1"}]`
[11:07] <cjp256> so I used `cmd` to bypass the format in a mergeable manner
[12:55] <Matt33> Hey guys, I was wondering how you can access the cloud-init dependencies.  I want to see if it runs before my cron daemon
[13:03] <waldi> Matt33: you look into the shipped service files. but please note that cloud-init runs several times with different tasks
[13:47] <holman> cjp256: Gotcha. Yeah I don't know of a better way unfortunately :/
[14:09] <humain> Hello, 
[14:09] <humain> I made test test on automatic debian automatic configuration. I tried the following configuration for the network but it does not work. Will you have documentation or some example for the network configuration?
[14:09] <humain> Thanks
[14:09] <humain> The testing code:
[14:09] <humain> network:
[14:09] <humain>   ethernets:
[14:09] <humain>     eth0:
[14:09] <humain>       set-name: eth0
[14:09] <humain>       dhcp4: false
[14:10] <humain>       adresses: 172.x.x.x/24
[14:10] <humain>       gateway4: 172.x.x.x
[14:10] <humain>       nameservers:
[14:17] <minimal> humain: you spelt "adresses" wrong, also why are you specifying "nameservers:" but with no values?
[14:18] <minimal> humain: cloud-init has extensive documentation regarding network configuration: https://cloudinit.readthedocs.io/en/latest/topics/network-config.html
[14:20] <cjp256> holman: I don't think we can change the behavior without breaking users.  Looking forward, there are couple potential options I can think of: (1) add a new flag to fs_setup to disable applying the config block [more strongly than overwrite: false] like null does for mounts and/or (2) add a new flag to Azure datasource to disable merging the default disk configs.  Any thoughts on that?
[14:22] <minimal> hmm, submit a question and then leave the channel 56 seconds later....... weird
[16:20] <holman> cjp256: Either option sounds fine to me. This would only really be required for people combining multiple configs, which is applicable outside the azure datasource. As long as it gets a decent explanation (describing semantic differences between new flag and overwrite) in the module docs, I think I lean slightly that direction.
[16:58] <minimal> just to be clear, regarding the "v2 interface matching when no MAC" commit, this issue affects all renderers on 22.3?
[22:28] <blackboxsw> [community-notice] minimal: correct `Fix v2 interface matching when no MAC` addresses any renderer on systems without Netplan installed. We will be cutting an upstream 22.3.1 verified release. that contains fixes for LP: #1986551(for all renderers where nameservers are specified in network config v2 without a corresponding match:macaddress) and LP: #1978543 (for ubuntu)
[22:28] <blackboxsw> while it should be a corner case network version: 2 config.... w/ nameservers and no mac-address. it's something to be aware of
[22:29] <blackboxsw> our hope was to cut the upstream 22.3.1 today/tomorrow once the addtiional review passes.
[22:30] <blackboxsw> given time of day we missed the window for today