-
Notifications
You must be signed in to change notification settings - Fork 8.3k
/
catalog-info.yaml
225 lines (214 loc) · 6.78 KB
/
catalog-info.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
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
---
apiVersion: backstage.io/v1alpha1
kind: Component
metadata:
name: kibana
description: Kibana is a user interface that lets you visualize your Elasticsearch data and navigate the Elastic Stack.
annotations:
backstage.io/source-location: url:https://github.com/elastic/kibana/tree/main
github.com/project-slug: elastic/kibana
github.com/team-slug: elastic/kibana-tech-leads
buildkite.com/project-slug: elastic/kibana
sonarqube.org/project-key: elastic_kibana_AYvOkAHeQZlFqhqWIr9
tags:
- typescript
- javascript
- dashboards
- metrics
- visualizations
- observability
links:
- title: Documentation
url: https://www.elastic.co/guide/en/kibana/current/index.html
spec:
type: monorepo
owner: group:kibana-tech-leads
lifecycle: production
---
apiVersion: backstage.io/v1alpha1
kind: Location
metadata:
name: kibana-buildkite-pipelines
description: A location re-routing file, pointing to individual buildkite pipeline definition files
spec:
type: url
target: https://github.com/elastic/kibana/blob/main/.buildkite/pipeline-resource-definitions/locations.yml
---
apiVersion: backstage.io/v1alpha1
kind: Resource
metadata:
name: kibana-tests-pipeline
description: Definition of the kibana pipeline
links:
- title: Pipeline
url: https://buildkite.com/elastic/kibana-tests
spec:
type: buildkite-pipeline
owner: group:kibana-tech-leads
system: buildkite
implementation:
apiVersion: buildkite.elastic.dev/v1
kind: Pipeline
metadata:
name: kibana-tests
description: Pipeline that tests the service integration in various environments
spec:
repository: elastic/kibana
pipeline_file: ./.buildkite/pipelines/quality-gates/pipeline.kibana-tests.yaml
provider_settings:
trigger_mode: none
teams:
kibana-operations:
access_level: MANAGE_BUILD_AND_READ
kibana-release-operators:
access_level: BUILD_AND_READ
cloud-tooling:
access_level: BUILD_AND_READ
everyone:
access_level: READ_ONLY
---
apiVersion: backstage.io/v1alpha1
kind: Component
metadata:
name: Kibana-UI-Service
description: Kibana UI Service provides the UX for visualizing Elasticsearch data. It is comprised of a client side for presentation and user event handling and a server side application for UX servicing and interaction with Elasticsearch.
annotations:
backstage.io/source-location: url:https://github.com/elastic/kibana/tree/main
github.com/project-slug: elastic/kibana
github.com/team-slug: elastic/kibana-tech-leads
buildkite.com/project-slug: elastic/kibana
tags:
- typescript
- javascript
- dashboards
- metrics
- visualizations
- observability
links:
- title: Documentation
url: https://www.elastic.co/guide/en/kibana/current/index.html
spec:
type: service
owner: group:kibana-tech-leads
lifecycle: production
system: control-plane
---
apiVersion: backstage.io/v1alpha1
kind: Component
metadata:
name: Kibana-Background-Tasks-Service
description: Kibana Background Tasks Service provides additional task processing parallelism for an instance of the Kibana UI Service. It is comprised of the same codebase as Kibana UI Service but is launched with an alternative configuration.
annotations:
backstage.io/source-location: url:https://github.com/elastic/kibana/tree/main
github.com/project-slug: elastic/kibana
github.com/team-slug: elastic/kibana-tech-leads
buildkite.com/project-slug: elastic/kibana
tags:
- typescript
- javascript
- dashboards
- metrics
- visualizations
- observability
links:
- title: Documentation
url: https://www.elastic.co/guide/en/kibana/current/index.html
spec:
type: service
owner: group:kibana-tech-leads
lifecycle: production
system: control-plane
---
# yaml-language-server: $schema=https://gist.githubusercontent.com/elasticmachine/988b80dae436cafea07d9a4a460a011d/raw/rre.schema.json
apiVersion: backstage.io/v1alpha1
kind: Resource
metadata:
name: buildkite-pipeline-kibana-kme-test
spec:
implementation:
apiVersion: buildkite.elastic.dev/v1
kind: Pipeline
metadata:
description: Temporary pipeline for testing Kibana KME work
name: kibana-kme-test
spec:
pipeline_file: .buildkite/scripts/pipelines/pull_request/pipeline.sh
provider_settings:
build_branches: false
build_pull_requests: true
publish_commit_status: false
trigger_mode: none
repository: elastic/kibana
teams:
kibana-operations:
access_level: MANAGE_BUILD_AND_READ
everyone:
access_level: READ_ONLY
owner: group:kibana-operations
type: buildkite-pipeline
---
# yaml-language-server: $schema=https://gist.githubusercontent.com/elasticmachine/988b80dae436cafea07d9a4a460a011d/raw/rre.schema.json
apiVersion: backstage.io/v1alpha1
kind: Resource
metadata:
name: buildkite-pipeline-kibana-sonarqube
description: Run a SonarQube scan
links:
- title: Pipeline
url: https://buildkite.com/elastic/kibana-sonarqube
spec:
type: buildkite-pipeline
owner: group:kibana-operations
system: buildkite
implementation:
apiVersion: buildkite.elastic.dev/v1
kind: Pipeline
metadata:
name: kibana / sonarqube
spec:
repository: elastic/kibana
provider_settings:
trigger_mode: none
schedules:
daily:
branch: main
cronline: "@daily"
pipeline_file: ".buildkite/pipelines/sonarqube.yml"
teams:
kibana-operations:
access_level: MANAGE_BUILD_AND_READ
everyone:
access_level: READ_ONLY
---
# yaml-language-server: $schema=https://gist.githubusercontent.com/elasticmachine/988b80dae436cafea07d9a4a460a011d/raw/rre.schema.json
apiVersion: backstage.io/v1alpha1
kind: Resource
metadata:
name: buildkite-pipeline-kibana-emergency-release
description: Emergency release
links:
- title: Pipeline
url: https://buildkite.com/elastic/kibana-emergency-release
spec:
type: buildkite-pipeline
owner: group:kibana-operations
system: buildkite
implementation:
apiVersion: buildkite.elastic.dev/v1
kind: Pipeline
metadata:
name: kibana / emergency release
spec:
repository: elastic/kibana
provider_settings:
trigger_mode: none
pipeline_file: ".buildkite/pipelines/emergency_release.yml"
teams:
kibana-operations:
access_level: MANAGE_BUILD_AND_READ
kibana-release-operators:
access_level: BUILD_AND_READ
everyone:
access_level: READ_ONLY
# Please avoid creating new kibana pipelines in this file to avoid bloating.
# Instead, create a new file in the pipeline-resource-definitions directory, and wire it in through the locations.yml file.