From 6e717f2e4418d9ecdcd58b010a053d433b7f9a80 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Florian=20Sch=C3=BCller?= Date: Thu, 30 Jul 2026 16:32:19 +0200 Subject: [PATCH 1/4] blueprint-reference: fix outdated FIPS support claim FIPS is no longer Edge-only; point readers at per-type supported_options in the image descriptions. --- docs/user-guide/01-blueprint-reference.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/docs/user-guide/01-blueprint-reference.md b/docs/user-guide/01-blueprint-reference.md index 28b0a1e77a8..df91b6a20ab 100644 --- a/docs/user-guide/01-blueprint-reference.md +++ b/docs/user-guide/01-blueprint-reference.md @@ -1727,8 +1727,9 @@ data = "" ### FIPS 🔵 🟤 {#fips} Enables/disables the system FIPS mode (disabled by default). -Currently only `edge-raw-image`, `edge-installer`, `edge-simplified-installer`, -`edge-ami` and `edge-vsphere` images support this customization. +Support depends on the image type — check the [image description](./09-image-descriptions/index.md) +`supported_options` list for `customizations.fips` (it is available on many +common disk image types, not only Edge). From a5f17186213b399617cec1c8aa48874a3fa6ea24 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Florian=20Sch=C3=BCller?= Date: Thu, 30 Jul 2026 16:32:30 +0200 Subject: [PATCH 2/4] blueprint-reference: document btrfs partitioning mode Align the partitioning_mode list with the Partitioning guide, which already describes btrfs alongside auto-lvm, raw, and lvm. --- docs/user-guide/01-blueprint-reference.md | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/docs/user-guide/01-blueprint-reference.md b/docs/user-guide/01-blueprint-reference.md index df91b6a20ab..38e8557c3b5 100644 --- a/docs/user-guide/01-blueprint-reference.md +++ b/docs/user-guide/01-blueprint-reference.md @@ -1347,15 +1347,14 @@ in the repository configuration. **GPG keys are not imported to the RPM database _See the section of the guide on [Partitioning](./07-partitioning.md) for more details._ The `customizations.partitioning_mode` variable can be used to select how the -disk image will be partitioned. `auto-lvm` will use raw unless there are one or -more [filesystem customizations](#filesystems) in which case it will use LVM. -`lvm` always uses LVM, even when there are no extra mountpoints. `raw` uses raw -partitions even when there are one or more mountpoints. +disk image will be partitioned. See the [Partitioning](./07-partitioning.md) +guide for full semantics. Supported modes: -- `auto-lvm` uses raw unless [filesystem customizations](#filesystems) are included. +- `auto-lvm` (default) uses raw unless [filesystem customizations](#filesystems) are included, in which case it uses LVM. - `raw` always uses raw partitions - `lvm` always uses LVM partitions +- `btrfs` converts the root partition to a Btrfs volume (extra mountpoints become subvolumes; see [Partitioning](./07-partitioning.md)) From 8be32e9efafa023a50b894506ee8d8d47941522f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Florian=20Sch=C3=BCller?= Date: Thu, 30 Jul 2026 16:32:39 +0200 Subject: [PATCH 3/4] blueprint-reference: fix hosted custom_repositories JSON example The array elements must be objects; the previous example was invalid JSON and would fail if copied into a compose request. --- docs/user-guide/01-blueprint-reference.md | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/docs/user-guide/01-blueprint-reference.md b/docs/user-guide/01-blueprint-reference.md index 38e8557c3b5..7047cfda232 100644 --- a/docs/user-guide/01-blueprint-reference.md +++ b/docs/user-guide/01-blueprint-reference.md @@ -1302,12 +1302,14 @@ enabled=true { "customizations": { "custom_repositories": [ - "id": "example", - "name": "Example repo", - "baseurl": [ "https://example.com/yum/download" ], - "check_gpg": true, - "gpgkey" : [ "https://example.com/public-key.asc" ], - "enabled": true + { + "id": "example", + "name": "Example repo", + "baseurl": [ "https://example.com/yum/download" ], + "check_gpg": true, + "gpgkey": [ "https://example.com/public-key.asc" ], + "enabled": true + } ] } } From d2b7934783ff2fe5a408caa38b2564234eeb704e Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Florian=20Sch=C3=BCller?= Date: Thu, 30 Jul 2026 16:37:07 +0200 Subject: [PATCH 4/4] blueprint-reference: clarify auto-lvm when plain vs LVM State both cases directly instead of an "unless" phrasing. --- docs/user-guide/01-blueprint-reference.md | 26 +++++++++++++++-------- 1 file changed, 17 insertions(+), 9 deletions(-) diff --git a/docs/user-guide/01-blueprint-reference.md b/docs/user-guide/01-blueprint-reference.md index 7047cfda232..12c1feacdda 100644 --- a/docs/user-guide/01-blueprint-reference.md +++ b/docs/user-guide/01-blueprint-reference.md @@ -1348,15 +1348,23 @@ in the repository configuration. **GPG keys are not imported to the RPM database _See the section of the guide on [Partitioning](./07-partitioning.md) for more details._ -The `customizations.partitioning_mode` variable can be used to select how the -disk image will be partitioned. See the [Partitioning](./07-partitioning.md) -guide for full semantics. - -Supported modes: -- `auto-lvm` (default) uses raw unless [filesystem customizations](#filesystems) are included, in which case it uses LVM. -- `raw` always uses raw partitions -- `lvm` always uses LVM partitions -- `btrfs` converts the root partition to a Btrfs volume (extra mountpoints become subvolumes; see [Partitioning](./07-partitioning.md)) +The `customizations.partitioning_mode` variable controls how filesystem +customizations change the image type’s **base** partition table. The base +layout itself depends on the image type: some defaults are plain partitions, +others already use LVM (for example Fedora Server) or Btrfs. + +To see a type’s default, open its [image description](./09-image-descriptions/index.md) +and inspect `partition_table` in the YAML (plain root shows a filesystem +`payload` with a `mountpoint`; LVM shows `logical_volumes`). + +Not every image type accepts `partitioning_mode` / `filesystem` — check that +page’s supported blueprint options list. + +Supported modes (when the image type allows them): +- `auto-lvm` (default) — keep the image type’s base layout when you do not add new mountpoints; if the base is plain and the blueprint adds new mountpoints via [filesystems](#filesystems), convert to LVM +- `raw` — keep plain partitions (never convert to LVM or Btrfs; unsupported if the base is already LVM) +- `lvm` — always LVM +- `btrfs` — always Btrfs for root (extra mountpoints become subvolumes; see [Partitioning](./07-partitioning.md))