After anaconda stopped creating default connections for unconfigured devices (https://issues.redhat.com/browse/INSTALLER-3088) we should review and reconsider the ONBOOT policy settings:

1) The current ONBOOT=no for connections created based on UI configuration (GUI: https://github.com/rhinstaller/anaconda/blob/809610cfb79a61da256c580b0e038c240c740ba9/pyanaconda/ui/gui/spokes/network.py#L587, check TUI) should be reconsidered. It no longer aligns with default for unconfigured devices which is NM autoconnections, ie ONBOOT=no. Also it will become probably inconsistent with WebUI (Cockpit network module).

2) The policy setting mechanisms at the end of installation (https://github.com/rhinstaller/anaconda/blob/809610cfb79a61da256c580b0e038c240c740ba9/pyanaconda/modules/network/network.py#L513) worked with assumption of existence of persistent profile for each (even unconfigured) device. I checked in https://issues.redhat.com/browse/INSTALLER-4519 that the surface affected by change of behavior caused by removing it should be really small but we still should update the code.

It would be great to create also upstream tests for UI configuration now that we are able to do it in scope of webui tests.