AutoYaST system clone

[josef Reidinger]

On Fri, 19 Mar 2021 13:37:09 +0000
"Reisenweber, Jörg" <Joerg.Reisenweber at btc-it-services.com> wrote:

> Hi there,

Hi Jorg,
it is intentional change and its goal is to remove some ambitious for xml elements.
In past there was config:type="list" for lists and for maps there are no type. And for string type situation is same. And this cause issue if you have empty string and empty map, both result in same <a></a> element and we have wrong type there. So in SP3 we use types everywhere beside string. And to make manual writting easier we add shortcut from config:type="list" to t="list". Of course we are backward compatible so if you omit t="map" and have some sub elements it will work. But for exporting we use map everywhere.

If you are interested in more details you can see it in blog posts:
https://yast.opensuse.org/blog/2020-04-20/sprint-97#xml-parser
https://yast.opensuse.org/blog/2020-05-29/sprint-99-100

Regarding autoyast and profile there are even more changes in SP3
like dynamic profiles - https://susedoc.github.io/doc-sle/main/html/SLES-autoyast/part-dynamic-profiles.html
or default validation of xml profiles. And new cli call to validate your profile including dynamic parts https://susedoc.github.io/doc-sle/main/html/SLES-autoyast/cha-autoyast-create-control-file.html#check-profile

I hope you will find it useful.

And of course if you are interested in more details, do not hesitate to ask or provide feedback about any changes we do.

Thanks
Josef

> 
> I was just trying to get started with AutoYaST for SLE 15 SP3 beta and generated an XML-Template from a running system with "yast clone_system". The resulting file has lots of 't="map=" or t="list"' in it, e.g.
> 
>   <firewall t="map">
>     <default_zone>public</default_zone>
>     <enable_firewall t="boolean">false</enable_firewall>
>     <log_denied_packets>off</log_denied_packets>
>     <start_firewall t="boolean">false</start_firewall>
>     <zones t="list">
>       <zone t="map">
>         <description>Unsolicited incoming network packets are rejected. Incoming packets that are related to outgoing network c
> onnections are accepted. Outgoing network connections are allowed.</description>
>         <interfaces t="list"/>
>         <masquerade t="boolean">false</masquerade>
>         <name>block</name>
>         <ports t="list"/>
>         <protocols t="list"/>
>         <services t="list"/>
>         <short>Block</short>
>         <target>%%REJECT%%</target>
>       </zone>
>       <zone t="map">
> …
> 
> This looks rather new to me. Or is this a bug? Can you shed some light on this?
> 
> Thanks
> Jörg