Configuration update for release 5.11.3

The instructions below are valid for Allure TestOps version 5.x.

Release 5.11.3 strictly requires PostgreSQL database version 15 or higher.

If the PostgreSQL version is below 15, Allure TestOps will fail to start with an exception.

Before upgrading to version 5.11.x, you need to ensure that you are using the correct version of PostgreSQL and update the configuration parameters accordingly.

How to update the configurations

Update the Helm Chart:
```
helm repo update
```

Update your values.yaml file accordingly to the actual Helm Chart's values.yaml template:

Open https://dl.qameta.io/ui/native/helm/testops/ and locate the TGZ archive with an ID of at least 5.11.0.
Download the archive.
Extract the values.yaml template with the command:
```
tar -xzvf testops-<5.11.XX>.tgz  testops/values.yaml
```
where instead of <5.11.XX> use the version number of the latest TGZ archive, for example, 5.11.3.

In the extracted values.yaml template, find the section related to the datasources for the migrations and copy the parameters to your values.yaml file.

The parameters you are looking for are the following (under the datasources: section):

migrationDatasource:
# This section's purpose is to make the data migrations inside the database less visible for the end users.
# System will allocate separate pool of the DB connections for the data migrations tasks and the migrations won't affect end users operations.
# maxDBMigrationConn defines the max connections number that will be used for the migrations tasks inside the database.
  maxDBMigrationConn: 2
# minDBMigrationIdle defines the min amount of connections to be kept in idle state. Leave it as it is unless recommended otherwise by the support
  minDBMigrationIdle: 0
# migrationSchedulerPoolSize defines the number of parallel threads that can be used for the migration tasks.
# The default value is 1, please do not increase this amount unless you have high workload and large database size.
  migrationSchedulerPoolSize: 1

Redeploy the application with the updated parameters.

Download the ZIP archive and extract the latest configuration files from it:

wget https://dl.qameta.io/artifactory/bin/docker-compose/testops-docker-compose.zip -O testops-compose.zip && unzip testops-compose.zip -d "testops"

Stop the Allure TestOps deployment:
```
docker compose down
```
Find the docker-compose.yml file which you used for the deployment of your configuration.
Rename this file (e.g., docker-compose.yml → docker-compose.old) and replace it with the docker-compose.yml file extracted from the archive.

If necessary (although not recommended), make adjustments to the docker-compose.yml file if you have altered the content of the previous file.
Start the deployment with the new docker-compose.yml file:
```
docker compose up -d
```

Alternatively, you can manually update the existing docker-compose.yml file as follows:

Open docker-compose.yml with any text editor.
Search for the string assumeMinServerVersion=11.
Replace the text as follows: assumeMinServerVersion=11 → assumeMinServerVersion=15.

Stop the installed application:
```
sudo systemctl stop testops
```
Open the configuration file /opt/testops/conf/testops.conf with any text editor.
Search for the string assumeMinServerVersion=11 and replace it with assumeMinServerVersion=15.
Update the application as described in the Upgrading section of the DEB/RPM packages installation documentation.
Run the application:
```
sudo systemctl start testops
```

If you have any doubts or the instructions above are not clear enough, please create a support request at https://help.qameta.io.