forked from airbytehq/airbyte-platform
-
Notifications
You must be signed in to change notification settings - Fork 0
/
flags.yml
51 lines (51 loc) · 1.85 KB
/
flags.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
flags:
- name: performance.backgroundJsonSchemaValidation
serve: false
- name: heartbeat.failSync
serve: false
- name: connectors.versionOverridesEnabled
serve: true
- name: heartbeat-max-seconds-between-messages
serve: "10800"
- name: use-new-notification-workflow
serve: false
- name: validation.removeValidationLimit
serve: false
- name: connection.columnSelection
serve: true
- name: refreshSchema.period.hours
serve: 0
- name: concurrent.source.stream.read
serve: false
- name: platform.add-scheduling-jitter
serve: false
- name: connectors.apm-enabled
serve: false
- name: connectors.useIconUrlInApiResponse
serve: true
# whether the platform will track destination timeouts. If set to 'true', then the platform will monitor if there has been
# a call to a destination that has taken more than the threshold defined in 'destination-timeout.maxSeconds', and if so,
# the platform will consider the destination to have timed out.
- name: destination-timeout-enabled
serve: true
# If set to 'true' and the platform detects a destination timeout, it will fail the sync. Otherwise, it will
# log a message and the sync will proceed.
- name: destination-timeout.failSync
serve: true
# the time the platform waits before it decides that a destination has timed out.
- name: destination-timeout.seconds
serve: 86400
- name: platform.inject-aws-secrets-to-connector-pods
serve: false
- name: platform.use-workload-api
serve: false
# Override used in order to run an acceptance test
context:
- type: "workspace"
include:
- "3d2985a0-a412-45f4-9124-e15800b739be"
- "1bdcfb61-219b-4290-be4f-12f9ac5461be"
- "3851861d-ac0b-440c-bd60-408cf9e7fc0e"
serve: true
- name: platform.fail-sync-on-invalid-checksum
serve: false