-
Notifications
You must be signed in to change notification settings - Fork 0
/
full.yaml
128 lines (124 loc) · 4.43 KB
/
full.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
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
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
---
# teams define the names, description, and members of engineering groups.
# teams are associated with services. These are the applications they build
# and maintain.
teams:
core:
description: Kong Financial Core team
users:
# services are the applications this team builds and maintains.
# Each service provides sufficient metadata to allow the orchestrator
# to apply service specific configurations and policies.
services:
KongFinancial/user:
# The service key supports a heirarchical name.
# This can support service specific patches by allowing patches to be
# specified in a matching folder structure.
name: user
vcs: "https://github.com/KongFinancial/user"
description: Kong Financial User management service
# The idea with spec-path is a pointer to an OAS3 spec file, which is used
# as a basis for GS configuration generation by the central automation
spec-path: openapi.yaml # relative to the vcs root
# The idea with kong-path is a pointer to a folder that contains
# service specific Kong configuration patches, applied by the central team's
kong-path: kong # relative to the vcs root
KongFinancial/account:
name: account
vcs: "https://github.com/KongFinancial/account"
description: Kong Financial Account management service
# What happens if there is no spec-path?
# spec-path: openapi.yaml
credit:
description: Kong Financial Credit team
users:
services:
KongFinancial/retail-cards:
name: retail-cards
vcs: https://github.com/KongFinancial/retail-cards
bb-fixed-income:
description: Bonobos Bank Fixed Income team
users:
services:
BonobosBank/fixed-income:
name: bb-fi
vcs: https://github.com/BonobosBank/fixed-income
# The organizations field defines the topology of the managed teams and services across
# one or more Konnect Organizations. This allows the orchestrator to
# manage consistent resource names and configurations
organizations:
# This key is arbitrary as it relates to Konnect, but it's recommended to relate to
# the organization name
kong-financial:
# API calls are scoped to organizations via the access-token used,
# thus, we don't need to track the org ID here.
# The access-token field supports a file, environment variable, or literal string type.
access-token:
type: file
value: $HOME/.konnect/20241120-kf-ko.spat
# ---
# type: env
# value: KONNECT_ACCESS_TOKEN
# ---
# type: literal # not recommended to prevent accidental exposure
# value: pat_ajbjdkfjhfhijajaj
environments:
# `type` is required and can be either: `DEV` or `PROD`
# These values are well known to the orchestrator and are used to determine the
# policies applied to resources
dev:
type: DEV
# `region` is required and must equal one of the Konnect supported region strings
region: us
teams:
core:
services:
- KongFinancial/user
- KongFinancial/account
credit:
services:
- KongFinancial/retail-cards
prd:
type: PROD
region: us
teams:
core:
services:
- KongFinancial/user
- KongFinancial/account
credit:
services:
- KongFinancial/retail-cards
# Let's pretend this is an acquired bank that the Kong Financial platform team is integrating
bonobos-bank:
access-token:
type: file
value: $HOME/.konnect/20241120-bb-ko.spat
environments:
dev:
type: DEV
region: us
teams:
core:
services:
- KongFinancial/user
- KongFinancial/account
bb-fixed-income:
services:
- BonobosBank/fixed-income
prd:
type: PROD
region: us
teams:
core:
services:
- KongFinancial/user
- KongFinancial/account
bb-fixed-income:
services:
- BonobosBank/fixed-income