Regenerated library to pick up latest schema changes

Author: petemoore

codegenerator/model/model-data.txt

@@ -3733,11 +3733,9 @@ https://www.npmjs.com/package/cron-parser.  For example:
  * `['0 0 1 * * *']` -- daily at 1:00 UTC
  * `['0 0 9,21 * * 1-5', '0 0 12 * * 0,6']` -- weekdays at 9:00 and 21:00 UTC, weekends at noon
 
-Hooks can be parametrized using JSON-e. The task definition in the hook is used as a JSON-e template,
-and the paramters are supplied as a JSON-e context. The result of rendeting the template and context is
-used as the task definition. Currently context can only be provided with the triggerHook method.
-You can find a complete description about how json-e works, here:
-https://github.com/taskcluster/json-e'
+The task definition is used as a JSON-e template, with a context depending on how it is fired.  See
+https://docs.taskcluster.net/reference/core/taskcluster-hooks/docs/firing-hooks
+for more information.'
 Base URL    = 'https://hooks.taskcluster.net/v1'
 Entry 0     =
     Entry Type        = 'function'
@@ -3869,7 +3867,11 @@ Entry 8     =
     Entry Input       = 'http://schemas.taskcluster.net/hooks/v1/trigger-context.json'
     Entry Output      = 'http://schemas.taskcluster.net/hooks/v1/task-status.json'
     Entry Title       = 'Trigger a hook'
-    Entry Description = 'This endpoint will trigger the creation of a task from a hook definition.'
+    Entry Description = 'This endpoint will trigger the creation of a task from a hook definition.
+
+The HTTP payload must match the hooks `triggerSchema`.  If it does, it is
+provided as the `payload` property of the JSON-e context used to render the
+task template.'
 Entry 9     =
     Entry Type        = 'function'
     Entry Method      = 'get'
@@ -3910,7 +3912,11 @@ Entry 11    =
     Entry Input       = 'http://schemas.taskcluster.net/hooks/v1/trigger-context.json'
     Entry Output      = 'http://schemas.taskcluster.net/hooks/v1/task-status.json'
     Entry Title       = 'Trigger a hook with a token'
-    Entry Description = 'This endpoint triggers a defined hook with a valid token.'
+    Entry Description = 'This endpoint triggers a defined hook with a valid token.
+
+The HTTP payload must match the hooks `triggerSchema`.  If it does, it is
+provided as the `payload` property of the JSON-e context used to render the
+task template.'
 Entry 12    =
     Entry Type        = 'function'
     Entry Method      = 'get'

src/main/java/org/mozilla/taskcluster/client/hooks/Hooks.java

@@ -27,11 +27,9 @@
  *  * `['0 0 1 * * *']` -- daily at 1:00 UTC
  *  * `['0 0 9,21 * * 1-5', '0 0 12 * * 0,6']` -- weekdays at 9:00 and 21:00 UTC, weekends at noon
  * 
- * Hooks can be parametrized using JSON-e. The task definition in the hook is used as a JSON-e template,
- * and the paramters are supplied as a JSON-e context. The result of rendeting the template and context is
- * used as the task definition. Currently context can only be provided with the triggerHook method.
- * You can find a complete description about how json-e works, here:
- * https://github.com/taskcluster/json-e
+ * The task definition is used as a JSON-e template, with a context depending on how it is fired.  See
+ * https://docs.taskcluster.net/reference/core/taskcluster-hooks/docs/firing-hooks
+ * for more information.
  *
  * @see "[Hooks API Documentation](https://docs.taskcluster.net/reference/core/hooks/api-docs)"
  */
@@ -159,6 +157,10 @@ public CallSummary<EmptyPayload, EmptyPayload> removeHook(String hookGroupId, St
 
     /**
      * This endpoint will trigger the creation of a task from a hook definition.
+     * 
+     * The HTTP payload must match the hooks `triggerSchema`.  If it does, it is
+     * provided as the `payload` property of the JSON-e context used to render the
+     * task template.
 
      * Required scopes:
      *   hooks:trigger-hook:<hookGroupId>/<hookId>
@@ -197,6 +199,10 @@ public CallSummary<EmptyPayload, TriggerTokenResponse> resetTriggerToken(String
 
     /**
      * This endpoint triggers a defined hook with a valid token.
+     * 
+     * The HTTP payload must match the hooks `triggerSchema`.  If it does, it is
+     * provided as the `payload` property of the JSON-e context used to render the
+     * task template.
      *
      * @see "[Trigger a hook with a token API Documentation](https://docs.taskcluster.net/reference/core/hooks/api-docs#triggerHookWithToken)"
      */