From 8b2850618d58cf1e91233ded49760d70afffb0be Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Adnan=20Hajdarevi=C4=87?= Date: Sat, 6 Jun 2015 14:36:10 +0200 Subject: [PATCH] Updated Hook Definition (markdown) --- Hook-Definition.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Hook-Definition.md b/Hook-Definition.md index 6b8176b..67aa56d 100644 --- a/Hook-Definition.md +++ b/Hook-Definition.md @@ -7,10 +7,11 @@ Hooks are defined as JSON objects. Please note that in order to be considered va * `execute-command` - specifies the command that should be executed when the hook is triggered * `command-working-directory` - specifies the working directory that will be used for the script when it's executed * `response-message` - specifies the string that will be returned to the hook initiator + * `include-command-output-in-response` - boolean whether webhook should wait for the command to finish and return the output and/or error as a response to the hook initiator * `parse-parameters-as-json` - specifies the list of arguments that contain JSON strings. These parameters will be decoded by webhook and you can access them like regular objects in rules and `pass-arguments-to-command`. * `pass-arguments-to-command` - specifies the list of arguments that will be passed to the command. Check [Referencing request values page](Referencing-Request-Values) to see how to reference the values from the request. If you want to pass a static string value to your command you can specify it as `{ "source": "string", "name": "argumentvalue" }` * `trigger-rule` - specifies the rule that will be evaluated in order to determine should the hook be triggered. Check [Hook rules page](Hook-Rules) to see the list of valid rules and their usage ## Examples -Check out [Hook examples page](Hook-Examples) for more complex examples of hooks. +Check out [Hook examples page](Hook-Examples) for more complex examples of hooks. \ No newline at end of file