This repository has been archived by the owner on Jan 5, 2019. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 11
/
Copy pathconfig.yml
87 lines (69 loc) · 2.8 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
77
78
79
80
81
82
83
84
85
86
87
defaults:
app:
publishMetaData: !env:bool PUBLISH_METADATA
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
tableName: !env AZURE_TABLE_NAME
cryptoKey: !env AZURE_CRYPTO_KEY
signingKey: !env AZURE_SIGNING_KEY
monitoring:
project: !env MONITORING_PROJECT
enable: !env:bool MONITORING_ENABLE
# 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: false
# Trust a forwarding proxy
trustProxy: false
# AWS SDK configuration for publication of schemas and references
aws:
# Access key id (typically configured using environment variables)
accessKeyId: !env AWS_ACCESS_KEY_ID
# Secret access key (typically configured using environment variables)
secretAccessKey: !env AWS_SECRET_ACCESS_KEY
# Default AWS region, this is where the S3 bucket lives
region: 'us-west-2'
# Lock API version to use the latest API from 2013, this is fuzzy locking
# but it does the trick...
apiVersion: '2014-01-01'
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:
publishMetaData: false
statsComponent: 'test-queue'
# four days in the future, so secrets are always expired
secretExpirationDelay: '4 days'
azure:
accountId: 'jungle'
tableName: 'SecretsTestTable'
cryptoKey: 'CNcj2aOozdo7Pn+HEkAIixwninIwKnbYc6JPS9mNxZk='
signingKey: 'REALULTIMATEPOWER.NET'
monitoring:
enable: false
server:
port: 60415