forked from taskcluster/taskcluster
-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathconfig.yml
More file actions
68 lines (55 loc) · 2.12 KB
/
config.yml
File metadata and controls
68 lines (55 loc) · 2.12 KB
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
defaults:
app:
secretsTableName: 'Secrets'
statsComponent: 'secrets'
# Time delay before expiring secrets, in readable format, see:
# taskcluster.fromNow, notice this should be negative!
secretExpirationDelay: '- 30 seconds'
# Taskcluster configuration
taskcluster:
rootUrl: !env TASKCLUSTER_ROOT_URL
# Taskcluster credentials for this server, allowing access to the Azure table,
# sentry, statsum, etc.
credentials:
clientId: !env TASKCLUSTER_CLIENT_ID
accessToken: !env TASKCLUSTER_ACCESS_TOKEN
azure:
accountId: !env AZURE_ACCOUNT_ID
cryptoKey: !env AZURE_CRYPTO_KEY
signingKey: !env AZURE_SIGNING_KEY
monitoring:
level: !env:optional LEVEL
errorConfig: !env:json:optional ERROR_CONFIG
# Server configuration
server:
# Port to listen for requests on
port: !env:number PORT
# Environment 'development' or 'production'
env: 'development'
# Force SSL, not useful when runnning locally
forceSSL: !env:bool FORCE_SSL
# Trust a forwarding proxy
trustProxy: false
staging:
app:
statsComponent: 'secrets-staging'
production:
server:
port: 80
env: 'production'
# We trust the proxy on heroku, as the SSL end-point provided by heroku
# is a proxy, so we have to trust it.
trustProxy: true
test:
app:
statsComponent: 'test-queue'
# four days in the future, so secrets are always expired
secretExpirationDelay: '4 days'
azure:
accountId: 'pamplemousse'
tableName: 'SecretsTestTable'
cryptoKey: 'CNcj2aOozdo7Pn+HEkAIixwninIwKnbYc6JPS9mNxZk='
signingKey: 'REALULTIMATEPOWER.NET'
server:
port: 60415
forceSSL: false