Git-ify YaST profiles #10

New Issue

Georg · 2022-06-26T14:54:07+02:00

Georg commented

2022-06-26 14:54:07 +02:00

Either here, or in a separate YaST repository, our AutoYaST profiles should be published. It makes no sense to have them public on http://deploy.squirrelcube.xyz but not utilize Git version control.

As we currently store Vx versions of the primary autoinst.xml file on the HTTP server, I would like to commit each version individually to the new Git location in order for the old history to be somewhat preserved.

However, additional AutoYaST, secondary, profiles are in place, which were not edited using this scheme, and will not see past history. Those will have to be be commited to Git in their recent version.

After everything is in Git, it needs to be ensured no local edits remain uncommitted!

Either here, or in a separate YaST repository, our AutoYaST profiles should be published. It makes no sense to have them public on http://deploy.squirrelcube.xyz but not utilize Git version control. As we currently store V*x* versions of the primary autoinst.xml file on the HTTP server, I would like to commit each version individually to the new Git location in order for the old history to be somewhat preserved. However, additional AutoYaST, secondary, profiles are in place, which were not edited using this scheme, and will not see past history. Those will have to be be commited to Git in their recent version. After everything is in Git, it needs to be ensured no local edits remain uncommitted!

Georg commented

2022-06-26 14:55:07 +02:00

The idea occured to me after creating autoinstV23.xml for openSUSE Leap 15.4 VPS deployments today.

The idea occured to me after creating [autoinstV23.xml](http://deploy.squirrelcube.xyz/autoinstV23.xml) for openSUSE Leap 15.4 VPS deployments today.

Sign in to join this conversation.