You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/checks/external_commands/_index.md
+14Lines changed: 14 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -110,6 +110,20 @@ restart_service = NET START "$ARG1$"
110
110
111
111
If your scripts are located within the `${scripts}` folder, you can specify them using relative paths, as demonstrated in the examples. SNClient will automatically obtain the absolute path for these scripts and use it for execution. Prior to running the scripts, SNClient configures the working directory to be ${shared-dir}.
112
112
113
+
114
+
#### Script Discovery
115
+
116
+
```
117
+
; Load all scripts in a given folder - Load all (${script path}/*) scripts in a given directory and use them as commands.
118
+
; Any executable file is considered a script. They do not have end with an script like extension.
119
+
; In windows, executable files cannot be discerned. It will add every file under the directory.
120
+
; Links are followed, and if they end up under script path, they will be added as a script.
121
+
; If path ends with ** its subdirectories will be searched as well.
122
+
script path = ${scripts}/autoinclude
123
+
```
124
+
125
+
Scripts can also be automatically discovered and added, without defining them individually. This uses the `script path` setting. There is no way to change the alias, as they will use the scripts name and extension for their alias.
126
+
113
127
#### Wrapped Scripts
114
128
115
129
Specify script templates used to define script commands. These templates are expanded by scripts located in the Wrapped Scripts section. Use `%SCRIPT%` to represent the actual script and `%ARGS%` for any provided arguments.
0 commit comments