Allow variable expansion on the "background_script" state property

didier-wenzek · didier-wenzek · commit 485b8e2ad9a0 · 2024-06-06T14:47:03.000+02:00
Signed-off-by: Didier Wenzek &lt;didier.wenzek@free.fr&gt;
diff --git a/crates/core/tedge_api/src/workflow/mod.rs b/crates/core/tedge_api/src/workflow/mod.rs
@@ -276,6 +276,13 @@ impl OperationAction {
                 },
                 handlers.clone(),
             ),
+            OperationAction::BgScript(script, handlers) => OperationAction::BgScript(
+                ShellScript {
+                    command: state.inject_values_into_template(&script.command),
+                    args: state.inject_values_into_parameters(&script.args),
+                },
+                handlers.clone(),
+            ),
             OperationAction::Operation(command, Some(script), input, handlers) => {
                 OperationAction::Operation(
                     state.inject_values_into_template(command),
diff --git a/docs/src/references/agent/operation-workflow.md b/docs/src/references/agent/operation-workflow.md
@@ -508,6 +508,9 @@ on_timeout = "timeout_restart"
 on_success = "successful_restart"
 ```
 
+As for regular scripts, the parameters of a background script can be populated from the current command state,
+as in `background_script = "sudo shutdown --reboot ${.payload.reboot_delay}"`
+
 #### Awaiting Sub-Command Completion
 
 When a sub `operation` is executed, the operation workflow moves to a waiting state which `action` must be `await-operation-completion`.
