From 0cca3a03f65ccfecb770793c0c761810b4227bfb Mon Sep 17 00:00:00 2001 From: Marcel Guzik Date: Thu, 12 Sep 2024 14:34:23 +0200 Subject: [PATCH] fixup! docs: reference tedge-write in config_update reference --- docs/src/references/agent/tedge-configuration-management.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/references/agent/tedge-configuration-management.md b/docs/src/references/agent/tedge-configuration-management.md index c5fc834109..1cea746303 100644 --- a/docs/src/references/agent/tedge-configuration-management.md +++ b/docs/src/references/agent/tedge-configuration-management.md @@ -217,7 +217,7 @@ Upon receiving a configuration update command, the agent performs the following 2. The agent then uses the `type` information (`mosquitto`) to to look up the target path from the `tedge-configuration-plugin.toml` file and applies the new configuration content to the corresponding `path`(`/etc/mosquitto/mosquitto.conf`). If `tedge` user/group does not have write permissions to the path and its parent directory, - [`tedge-write`](../tedge-write.md) will be used for permission elevation. + [`tedge-write`](../tedge-write.md) will be used in combination with `sudo` for permission elevation. Throughout the process, the agent updates the command status via MQTT by publishing a retained message to the same `//cmd/config_update/` topic