Public bug reported:

Request
-------
We want Subiquity to grow built-in support for selecting which groups the 
primary user should belong to.
This will only be available to autoinstall users and will take the form of a 
new directive called "groups" in the autoinstall identity section.

We are past FF for resolute, so I would like to request an exception.

Why Needed
----------
In resolute, we have added builtin support for creating the primary user 
*during* the installation, instead of relying on cloud-init (which operates on 
first boot) like we used to (see bug 2090834).

We want people to move away from cloud-init and use the built-in
mechanism. Unfortunately, unlike cluod-init, the new mechanism did not
support specifying the list of groups that the primary user should
belong to. This is a blocker for some people.

With most of our autoinstall user-base running Ubuntu LTSe only,
delaying the addition of groups support will significantly delay the
adoption of the new mechanism.

What changed
------------
People using autoinstall will now be able to specify extra groups or to 
overwrite hard-coded groups (i.e., admin, sudo) using one of the following 
syntax:

  # Add the user to the wireshark group in addition to hard-coded groups
  groups: {append: [wireshark]}

  # Two equivalent ways to specify the list of groups, ignoring hard-coded 
values (i.e., sudo, admin)
  groups: [sudo, admin, lpadmin]
  groups: {override: [sudo, admin, lpadmin]}

The behavior for interactive installations (using Subiquity's TUI or
ubuntu-desktop-bootstrap) stays unchanged. The default behavior (when
the groups directive is not specified) is also unchanged.

Code to be merged
-----------------
https://github.com/canonical/subiquity/pull/2265

** Affects: subiquity
     Importance: Undecided
         Status: New

** Affects: subiquity (Ubuntu)
     Importance: Undecided
         Status: New

** Also affects: subiquity (Ubuntu)
   Importance: Undecided
       Status: New

** Description changed:

  Request
  -------
  We want Subiquity to grow built-in support for selecting which groups the 
primary user should belong to.
- This will only be available to autoinstall users and will the form of a new 
directive called "groups" in the autoinstall identity section.
+ This will only be available to autoinstall users and will take the form of a 
new directive called "groups" in the autoinstall identity section.
  
  We are past FF for resolute, so I would like to request an exception.
  
  Why Needed
  ----------
  In resolute, we have added builtin support for creating the primary user 
*during* the installation, instead of relying on cloud-init (which operates on 
first boot) like we used to (see bug 2090834).
  
  We want people to move away from cloud-init and use the built-in
  mechanism. Unfortunately, unlike cluod-init, the new mechanism did not
  support specifying the list of groups that the primary user should
  belong to. This is a blocker for some people.
  
  With most of our autoinstall user-base running Ubuntu LTSe only,
  delaying the addition of groups support will significantly delay the
  adoption of the new mechanism.
  
  What changed
  ------------
  People using autoinstall will now be able to specify extra groups or to 
overwrite hard-coded groups (i.e., admin, sudo) using one of the following 
syntax:
  
-   # Add the user to the wireshark group in addition to hard-coded groups
-   groups: {append: [wireshark]}
+   # Add the user to the wireshark group in addition to hard-coded groups
+   groups: {append: [wireshark]}
  
-   # Two equivalent ways to specify the list of groups, ignoring hard-coded 
values (i.e., sudo, admin)
-   groups: [sudo, admin, lpadmin]
-   groups: {override: [sudo, admin, lpadmin]}
+   # Two equivalent ways to specify the list of groups, ignoring hard-coded 
values (i.e., sudo, admin)
+   groups: [sudo, admin, lpadmin]
+   groups: {override: [sudo, admin, lpadmin]}
  
  The behavior for interactive installations (using Subiquity's TUI or
  ubuntu-desktop-bootstrap) stays unchanged. The default behavior (when
  the groups directive is not specified) is also unchanged.
  
- 
  Code to be merged
  -----------------
  https://github.com/canonical/subiquity/pull/2265

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2143141

Title:
  [Ffe] Allow autoinstall users to specify groups

To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/2143141/+subscriptions


-- 
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to