Skip to content

blueprint-reference: add note describing new groups behaviour #188

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
supakeen merged 1 commit into from
Feb 4, 2026
Merged

blueprint-reference: add note describing new groups behaviour #188

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/user-guide/01-blueprint-reference.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -558,6 +558,8 @@ An *optional* list of objects that contain the following attributes:
- `name` a **required** string that sets the name of the group.
- `gid` a **required** integer that sets the id of the group.

*Note: Collisions caused by duplicate names or GIDs will be resolved automatically at build time. This includes system groups created by packages. Therefore, adding a group with a name that already exists on the system will have no effect. When specifying a GID that is already used by another group, another unique GID is chosen.*

<Tabs values={tabValuesAll} >
<TabItem value="on-premises" >
```toml
Expand Down