forked from taskcluster/taskcluster-hooks
-
Notifications
You must be signed in to change notification settings - Fork 0
/
config.yml
76 lines (74 loc) · 2.45 KB
/
config.yml
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
defaults:
# defaults outlining all configuration options and some sane defaults
app:
component: hooks
hookTable: !env HOOK_TABLE_NAME
publishMetaData: !env:bool PUBLISH_METADATA
scheduler:
pollingDelay: 60000
influx:
connectionString: !env INFLUX_CONNECTION
maxDelay: 300
maxPendingPoints: 300
azureTable:
account: !env AZURE_ACCOUNT
signingKey: !env TABLE_SIGNING_KEY
cryptoKey: !env TABLE_CRYPTO_KEY
taskcluster:
authBaseUrl: null
credentials:
clientId: !env TASKCLUSTER_CLIENT_ID
accessToken: !env TASKCLUSTER_ACCESS_TOKEN
server:
port: !env:number PORT
publicUrl: !env PUBLIC_URL
env: !env NODE_ENV
forceSSL: !env:bool FORCE_SSL
trustProxy: false
#pulse:
# username: !env PULSE_USERNAME
# password: !env PULSE_PASSWORD
aws:
ses:
# Credentials with access to SES to send hook failure emails
accessKeyId: !env AWS_ACCESS_KEY_ID
secretAccessKey: !env AWS_SECRET_ACCESS_KEY
region: us-east-1
params:
Source: taskcluster-hooks@mozilla.com
validator:
# Credentials with access to references/schemas.taskcluster.net if you wish
# to publish meta-data
accessKeyId: !env AWS_ACCESS_KEY_ID
secretAccessKey: !env AWS_SECRET_ACCESS_KEY
region: us-west-2
apiVersion: 2014-01-01
production:
taskcluster:
authBaseUrl: https://auth.taskcluster.net/v1
server:
publicUrl: https://hooks.taskcluster.net
env: production
forceSSL: true
trustProxy: true
test:
# See user-config-example.yml for secrets credentials required for tests
app:
component: hooks-tests
hookTable: HooksTestTable2
publishMetaData: false
scheduler:
pollingDelay: 5000
azureTable:
# use in-memory fake Azure by default; you can override in user-config.yml
# this with a real account together with setting `taskcluster.credentials`
# to test against the real Azure Table Storage.
account: 'inMemory'
signingKey: 'not a secret'
cryptoKey: 'AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA='
server:
port: 60401
publicUrl: 'http://localhost:60401'
env: development
forceSSL: false
trustProxy: false