fix(helm chart): correctly set MAX_OBJECT_SIZE_MB & fix typo in connectionCreateTimeoutMillis (#4993)

This commit is contained in:
Iain Sproat
2025-06-26 19:10:40 +01:00
committed by GitHub
parent fd1a3cf341
commit 5e6b58e821
4 changed files with 5 additions and 5 deletions
@@ -139,7 +139,7 @@ spec:
{{- if (not .Values.featureFlags.nextGenFileImporterEnabled) }}
# DEPRECATED
- name: MAX_OBJECT_SIZE_MB
value: {{ .Values.objects.max_object_size_mb | quote }}
value: {{ .Values.server.max_object_size_mb | quote }}
{{- end }}
{{- if (and .Values.featureFlags.workspacesMultiRegionEnabled (not .Values.featureFlags.nextGenFileImporterEnabled)) }}
- name: FF_WORKSPACES_MULTI_REGION_ENABLED
+1 -1
View File
@@ -286,7 +286,7 @@
"description": "The maximum time in milliseconds to wait for a connection to be acquired from the connection pool.",
"default": 15000
},
"connectionCreationTimeoutMillis": {
"connectionCreateTimeoutMillis": {
"type": "number",
"description": "The maximum time in milliseconds to wait for a new connection to be created in the connection pool. Should be less than the acquisition timeout, as a new connection may need to be created then acquired.",
"default": 5000
+2 -2
View File
@@ -223,9 +223,9 @@ db:
## @param db.connectionAcquisitionTimeoutMillis The maximum time in milliseconds to wait for a connection to be acquired from the connection pool.
##
connectionAcquisitionTimeoutMillis: 15000
## @param db.connectionCreationTimeoutMillis The maximum time in milliseconds to wait for a new connection to be created in the connection pool. Should be less than the acquisition timeout, as a new connection may need to be created then acquired.
## @param db.connectionCreateTimeoutMillis The maximum time in milliseconds to wait for a new connection to be created in the connection pool. Should be less than the acquisition timeout, as a new connection may need to be created then acquired.
##
connectionCreationTimeoutMillis: 5000
connectionCreateTimeoutMillis: 5000
## @param db.knexAsyncStackTracesEnabled If enabled, will provide better stack traces for errors arising out of knex operations
##
knexAsyncStackTracesEnabled: false