Skip to content

Commit db44fcb

Browse files
reuse-configuration: convert UI/CLI subsections to tabs
Replace the H3 split between "In the Viam app" and "With the CLI" with a {{< tabs >}} pair. Same content; tabs frame the two flows as alternatives.
1 parent 3c0436c commit db44fcb

1 file changed

Lines changed: 7 additions & 2 deletions

File tree

docs/fleet/reuse-configuration.md

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -56,7 +56,8 @@ Click **Save** after adding and configuring your resources.
5656

5757
## Apply a fragment to a machine
5858

59-
### In the Viam app
59+
{{< tabs >}}
60+
{{% tab name="Viam app" %}}
6061

6162
1. Navigate to your machine's **CONFIGURE** tab.
6263
1. Click **+** and select **Configuration block**.
@@ -67,7 +68,8 @@ Click **Save** after adding and configuring your resources.
6768

6869
The fragment's resources now appear on the machine's configuration page. The machine downloads and applies the configuration on its next sync.
6970

70-
### With the CLI
71+
{{% /tab %}}
72+
{{% tab name="CLI" %}}
7173

7274
```sh {class="command-line" data-prompt="$"}
7375
viam machines part fragments add --part=<part-id> --fragment=<fragment-name-or-id>
@@ -79,6 +81,9 @@ If you omit `--fragment`, the CLI prompts you to pick a fragment interactively f
7981

8082
To apply a fragment across many machines, see [Automate with scripts](/cli/automate-with-scripts/).
8183

84+
{{% /tab %}}
85+
{{< /tabs >}}
86+
8287
### Avoid resource name conflicts with a prefix
8388

8489
If a machine already has a resource with the same name as one in the fragment, or if you apply the same fragment twice, you need a prefix to avoid name collisions.

0 commit comments

Comments
 (0)