This is a draft document that was built and uploaded automatically. It may document beta software and be incomplete or even incorrect. Use this document at your own risk.
Documented full support for bonding, bridge, and VLAN network interfaces converted
from AutoYaST profiles, including how Agama detects each interface type and the
bootproto and startmode mappings.
Corrected the services-manager/default_target
mapping: Agama uses systemctl set-default, not
set-target.
The bonding-conversion warning now describes the issue without implying a fixed timeline. Verify your Agama version before relying on automatic bonding conversion.
Clarified that starting an unattended installation with an AutoYaST profile does not
require manually running agama config generate first: pointing
inst.auto, or one of Agama's predefined profile locations,
directly at an AutoYaST profile triggers the same conversion automatically.
Corrected several AutoYaST-to-Agama field mappings to match the current Agama release, including software repositories, network interfaces, zFCP devices, and user SSH keys.
Initial version. This article was split out of Automated Installation Using Agama to keep AutoYaST-specific compatibility and migration information separate from the general profile workflow.