Agama Users (in Unattended mode): Only root and the first user are supported

[kobliha]

I understand that this is still an open question: How much should Agama be backward-compatible. Anyway, the point is that more users are definitely being supported and used by customers in AutoYaST and we should try hard to get more data / decision about the to-be supported scenario(s).

The answer, on the other hand, should not be based on, e.g., having the functionality currently written in Perl. If it's needed, it's needed and we have to find a way. The issue exists as a topic-opener and it's mean for gathering feedback too.

[imobachgs]

If you do not mind, I will move this issue to a discussion. We can create issues when we know what we decide what we are going to implement.

[imobachgs]

I have the same question, especially regarding users. In general, I do not like how users are handled in AutoYaST. Most of the users you can find on a typical system are already created by their own packages. So, once you install the same packages, you do not need to create them at all. The problem is that if you clone a system, you get the full list of users/groups. For that reason, we introduced the "compact" mode in the past, so only non-system users are cloned.

But is creating a single user (first user) and the root authentication mechanism enough? Well, when it comes to the ideas behind Agama, it should be. Any extra stuff should be handled after the first boot (out of Agama's territory). But I can understand that if you are using an AutoYaST profile, things might be different.

Regarding this topic, I have some questions:

• Do we want to open the door to enable different features, depending on whether you are doing an unattended or manual installation? Well, we are already doing that by supporting scripts.
• Should we extend the UI to support creating multiple users?
• Or should we support this feature only in AutoYaST mode?

OK, more questions and no answers, but the topic is worth a discussion 😉

[kobliha]

I have another question: What about software? AutoYaST supports selecting particular packages, but Agama supports only patterns. If we support 3rd party add-ons/repos, then we may need to support packages (at least) in unattended more too. And those repositories (URLs) actually as well.