From 91a850942f32cda8b00ff63b594a1125905feda2 Mon Sep 17 00:00:00 2001 From: Faraj Farook Date: Fri, 1 Jun 2018 13:57:57 +1000 Subject: [PATCH] Fix on link --- docs/Hook-Definition.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/Hook-Definition.md b/docs/Hook-Definition.md index 929e922..4ff03f0 100644 --- a/docs/Hook-Definition.md +++ b/docs/Hook-Definition.md @@ -16,7 +16,7 @@ Hooks are defined as JSON objects. Please note that in order to be considered va * `pass-environment-to-command` - specifies the list of arguments that will be passed to the command as environment variables. If you do not specify the `"envname"` field in the referenced value, the hook will be in format "HOOK_argumentname", otherwise "envname" field will be used as it's name. 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", "envname": "SOMETHING", "name": "argumentvalue" }` * `pass-file-to-command` - specifies a list of entries that will be serialized as a file. Incoming [data](Referencing-Request-Values.md) will be serialized in a request-temporary-file (otherwise parallel calls of the hook would lead to concurrent overwritings of the file). The filename to be addressed within the subsequent script is provided via an environment variable. Use `envname` to specify the name of the environment variable. If `envname` is not provided `HOOK_` and the name used to reference the request value are used. Defining `command-working-directory` will store the file relative to this location, if not provided, the systems temporary file directory will be used. If `base64decode` is true, the incoming binary data will be base 64 decoded prior to storing it into the file. By default the corresponding file will be removed after the webhook exited. - * `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 + * `trigger-rule` - specifies the rule that will be evaluated in order to determine should the hook be triggered. Check [Hook rules page](Hook-Rules.md) to see the list of valid rules and their usage * `trigger-rule-mismatch-http-response-code` - specifies the HTTP status code to be returned when the trigger rule is not satisfied ## Examples