From 8c33611247c9851caf75c03cc1e2028929fb6710 Mon Sep 17 00:00:00 2001 From: dplore Date: Thu, 29 Aug 2024 11:56:25 -0700 Subject: [PATCH] revise bootz configuration items to boot_config items --- rpc/gnmi/gnmi-union_replace.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/rpc/gnmi/gnmi-union_replace.md b/rpc/gnmi/gnmi-union_replace.md index f426d73..59ab332 100644 --- a/rpc/gnmi/gnmi-union_replace.md +++ b/rpc/gnmi/gnmi-union_replace.md @@ -500,9 +500,10 @@ special case of dynamic configuration and is managed by gNSI. Configuration necessary to boot and make a factory default NOS manageable by gNMI is defined as bootz configuration. -bootz configuration items can be expressed as OC, NY and CLI. Bootz defines an -order (or precedence) to apply the configuration name spaces to the NOS. The -order is dynamic configuration, followed by [boot_config](https://github.com/openconfig/bootz/blob/e0eb604d8e7e089ecf0d4553cce79de769328173/server/entitymanager/proto/entity.proto#L55) +bootz [boot_config](https://github.com/openconfig/bootz/blob/e0eb604d8e7e089ecf0d4553cce79de769328173/server/entitymanager/proto/entity.proto#L55) +can be expressed as OC, NY and CLI. Bootz defines an order (or precedence) +to apply the configuration name spaces to the NOS. The order is dynamic +configuration, followed by [boot_config](https://github.com/openconfig/bootz/blob/e0eb604d8e7e089ecf0d4553cce79de769328173/server/entitymanager/proto/entity.proto#L55) configuration, followed by gNSI configuration. That is, first apply dynamic configuration, then apply the boot_config (set by bootz) which may override dynamic configuration. Finally, apply gNSI configuration which may override