Skip to content
This repository was archived by the owner on Jan 5, 2019. It is now read-only.
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 0 additions & 6 deletions schemas/v1/create-hook-request.yml
Original file line number Diff line number Diff line change
Expand Up @@ -8,12 +8,6 @@ properties:
hookId: {$const: hookId}
metadata: {$ref: "hook-metadata.json#"}
schedule:
# It would be prettier with:
# {$ref: "http://schemas.taskcluster.net/hooks/v1/schedule.json#"}
# but it breaks "default" handling, schema library is a bit sketchy when it
# come to the "default" keyword.. I'm looking at an alernative that is
# both faster and implements "default" correctly.
# (there corner cases with anyof, and $ref that isn't handled well.)
description: |
Definition of the times at which a hook will result in creation of a task.
If several patterns are specified, tasks will be created at any time
Expand Down
7 changes: 3 additions & 4 deletions src/exchanges.js
Original file line number Diff line number Diff line change
Expand Up @@ -7,10 +7,9 @@ let exchanges = new Exchanges({
serviceName: 'hooks',
apiVersion: 'v1',
description: [
'The hooks service, typically available at `hooks.taskcluster.net`',
'is responsible for creating tasks at specific times or in .',
'response to webhooks and API calls.Using this exchange allows us',
'to make hooks which repsond to particular pulse messages',
'The hooks service is responsible for creating tasks at specific times or',
'in . response to webhooks and API calls.Using this exchange allows us to',
'make hooks which repsond to particular pulse messages',
'',
'These exchanges provide notifications when a hook is created, updated',
'or deleted. This is so that the listener running in a different hooks ',
Expand Down