Comment 19 for bug 1991261

Specific to your question in #16
"Anyway, onto the questions. Will this break anyone who is tweaking their kernel command line to use a networked seed?"

What `dsmode:local` vs `dsmode:net` tells cloud-init whether or not the datasource environment is considered 'up and available' and whether it can run supplemental user-data parts such as:
- ShellScriptByFreqPartHandler
- BootHookPartHandler

What this translates too is anyone providing the following user-data types would see those types run slightly before network is fully configured on the system, so network egress operations on complex environments may result in timeouts
- https://cloudinit.readthedocs.io/en/latest/topics/format.html?highlight=boothook#cloud-boothook
- https://cloudinit.readthedocs.io/en/latest/topics/format.html#user-data-script

This shift is probably not an issue for most use-cases of cloud-init. A number of clouds have transitioned to init-local dsmode timeframe from init-network because of the slight speedup in boot time by emitting full network configuration prior to the system network being brought up.