From 956de687fcbacacb78aa1c02540c94e5275178b8 Mon Sep 17 00:00:00 2001 From: Naomi Pentrel <5212232+npentrel@users.noreply.github.com> Date: Thu, 16 Jan 2025 15:03:39 +0100 Subject: [PATCH] DOCS-1848: Support nested fragmentes --- docs/manage/fleet/reuse-configuration.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/manage/fleet/reuse-configuration.md b/docs/manage/fleet/reuse-configuration.md index 9f2f1f14ad..ccb2ab1b56 100644 --- a/docs/manage/fleet/reuse-configuration.md +++ b/docs/manage/fleet/reuse-configuration.md @@ -26,7 +26,6 @@ Fragments are a way of sharing and managing [machine configurations](/operate/ge For example, if you have a fleet of rovers that uses the same hardware, you could use a fragment to configure the motors, base component, camera, and all other resources for all rovers. If some of the rovers have a slightly different configuration, you can overwrite the configuration for just those {{< glossary_tooltip term_id="resource" text="resources" >}} of those rovers. - If one rover has an arm attached, you can add the rover configuration fragment (including the motors, camera, and base components), and then configure the arm on just that one rover. ## Create a fragment @@ -40,6 +39,8 @@ You must be an [organization owner](/manage/manage/rbac/) to create fragments fo Start by configuring one of your machines. In the [Viam app](https://app.viam.com), use the **CONFIGURE** tab to build a configuration for all resources you want to use on all your machines. +You can use all available resources except [triggers](/data-ai/data/advanced/alert-data/) in the configuration for your machine. +This means you can also use fragments inside a fragment. {{}}