From 7f5d9f536437ae3e818198cf879e5134a81ca29f Mon Sep 17 00:00:00 2001 From: akloeckner Date: Thu, 1 Nov 2018 09:38:44 +0100 Subject: [PATCH] Templates only for arguments. (#7280) --- source/_components/shell_command.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_components/shell_command.markdown b/source/_components/shell_command.markdown index bb280f91220..b50d8f00a0c 100644 --- a/source/_components/shell_command.markdown +++ b/source/_components/shell_command.markdown @@ -30,7 +30,7 @@ Configuration variables: - Alias for the command - Command itself. -The commands can be dynamic, using templates to insert values for arguments. When using templates, shell_command runs in a more secure environment which doesn't allow any shell helpers like automatically expanding the home dir `~` or using pipe symbols to run multiple commands. +The commands can be dynamic, using templates to insert values for arguments. When using templates, shell_command runs in a more secure environment which doesn't allow any shell helpers like automatically expanding the home dir `~` or using pipe symbols to run multiple commands. Similarly, only content after the first space can be generated by a template. This means the command name itself cannot be generated by a template, but it must be literally provided. Any service data passed into the service call to activate the shell command will be available as a variable within the template.