feat(server options): allow connection timeouts to be configured #3701
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description & motivation
Postgres client configuration parameters were hard coded and could not be configured. This PR allows them to be configured by the server operator.
Changes:
POSTGRES_CONNECTION_CREATE_TIMEOUT_MILLIS
andPOSTGRES_CONNECTION_ACQUIRE_TIMEOUT_MILLIS
db.connectionAcquisitionTimeoutMillis
anddb.connectionCreationTimeoutMillis
configuration parameters and configure environment variablespostgresMaxConnections
to be configured for fileimport service, preview service, and webhook service. These were previously configurable via environment variable but not via the Helm Chart.process.env['key']
syntax overprocess.env.key
syntax.To-do before merge:
Screenshots:
Validation of changes:
Checklist:
References