From 6a18561760aaefbe64a15af7aaaa00417ef54923 Mon Sep 17 00:00:00 2001 From: Camila Macedo Date: Wed, 4 Oct 2023 18:35:34 +0100 Subject: [PATCH] Note in 'Production Targets' section: Users are now informed about the necessity of obtaining the targets key, a prerequisite to proceed. Signed-off-by: Camila Macedo Co-authored-by: vkhoroz --- source/reference-manual/ota/production-targets.rst | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/source/reference-manual/ota/production-targets.rst b/source/reference-manual/ota/production-targets.rst index c66b5c153..347244d06 100644 --- a/source/reference-manual/ota/production-targets.rst +++ b/source/reference-manual/ota/production-targets.rst @@ -35,7 +35,9 @@ Waves allow Factory operators to control an exact time when devices see a new ve Performing a Production OTA --------------------------- -A user should define a process to select CI builds which need to be delivered to production devices. +A customer should define a process to select CI builds which need to be delivered to production devices. +Every user performing production OTAs should generate their personal :ref:`offline TUF targets key ` used to sign production targets. + Let's assume a user selected a CI build version 42 as ready to be run in production. To start the production release process, a user would create a new wave using the below command::