It may be required for the use in installer. The device oriented approach (used in Gtk Anaconda GUI) required profile management in the backend, and as a consequence made integration with other tools in the environment difficult to impossible.

Especially without Anaconda backend connections management (using NetworkDeviceConfiguration objects) we need to be more flexible in Connection editing, for example for installer to allow to edit connections created via boot options or kickstart.

Current Cockpit network module UI seems to be insufficient for 2 network devices, editing common default Wired Connection profile for both devices.

See the decisions and principles for details. Adding screenshots for Anaconda, Cockpit (device oriented), and Agama (connection oriented) from the document for idea.