-
Notifications
You must be signed in to change notification settings - Fork 0
/
brigade-github-app-values.example.yaml
60 lines (53 loc) · 1.73 KB
/
brigade-github-app-values.example.yaml
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
rbac:
enabled: true
serviceAccount:
create: true
name:
## Image configuration
registry: brigadecore
name: brigade-github-app
## Image tags in this chart default to the value specified by appVersion in Chart.yaml
# tag: latest
# pullPolicy: "Always"
service:
name: brigade-github-app
type: LoadBalancer
externalPort: 80
internalPort: 7746
#ingress:
# enabled: true
## Used to create an Ingress record.
# hosts:
# - uuid.qicoo.tokyo
#annotations:
# kubernetes.io/ingress.class: nginx
# kubernetes.io/tls-acme: "true"
#tls:
## Secrets must be manually created in the namespace.
#- secretName: gh-app-tls
# hosts:
# - uuid.qicoo.tokyo
gateway:
## The author associations who are allowed to have PRs built
## Classes are: COLLABORATOR, CONTRIBUTOR, OWNER, NONE, MEMBER, FIRST_TIMER, FIRST_TME_CONTRIBUTOR
## See https://developer.github.com/v4/enum/commentauthorassociation/
## To completely disable pull request builds, leave this list blank.
allowedAuthorRoles:
- OWNER
- MEMBER
- COLLABORATOR
github:
## The x509 PEM-formatted keyfile GitHub issued for you App.
key: |
FILL YOUR KEY
## This represents the unique ID for a GitHub App
## The value can be retrieved from the main App page or any inbound webhook payloads
appID: FILL YOUR APP
## Trigger a Check Suite on Pull Requests
## This will need to be set to true to enable running Check Suites on PRs originating from forks
checkSuiteOnPR: true
## Set a defaultSharedSecret if you want to use this one instance of the
## Github gateway with multiple Brigade projects. Leave the shared secret field
## blank in project-level configuration and this default will be used.
# defaultSharedSecret:
check_suite: created