Different network devices when using network attach and network attach-profile

[fcavro]

Required information

• Distribution: Arch Linux
• Distribution version: rolling
• The output of "incus info" or if that fails:
  • Kernel version: 6.8.9-arch1-2
  • Incus version: 6.1

Issue description

Attaching instances to a network results in a different network device configuration compared to attaching profiles to it.

After attaching an instance to a network, the network device looks like this:

devices:
  eth1:
    name: eth1
    network: testbr0
    type: nic

But when attaching a profile to the network, the network device of the profile (or of an instance using the profile) looks like this:

devices:
  eth1:
    name: eth1
    nictype: bridged
    parent: testbr0
    type: nic

I would've expected, that the profile's network device is configured via the network name (like when attaching an instance) and not via an explicitly bridged interface.

Is this intentional behavior?

Steps to reproduce

1. incus network create testbr0
2. incus network create testbr1
3. incus profile create testprofile
4. incus launch images:debian/12 testinstance -p default -p testprofile
5. incus network attach-profile testbr0 testprofile viaprofile eth1
6. incus network attach testbr1 testinstance viainstance eth2
7. incus config show --expanded testinstance

   [...]
   viainstance:
     name: eth2
     network: testbr1
     type: nic
   viaprofile:
     name: eth1
     nictype: bridged
     parent: testbr0
     type: nic
   [...]