It's strongly recommended to deploy the database outside of Allure Testops deployment as based on our experience running in a container/pod could severely degrade the performance of the database in case of high load generated by the automated tests.
Allure Testops uses 2 databases - uaa for user management and report to store all the tests related data.
After the 1st of March 2024, we'll discontinue the support of PostgreSQL 14 and PostgreSQL 15 will become the mandatory version.
Both statements mean, we do not perform any tests during the development and QA stages with any PostgreSQL versions except mandatory one, hence we cannot guarantee Allure Testops will be able to perform or start with PostgreSQL versions different from the mandatory one.
It's highly recommended using enterprise grade SSD for the database.
Creating the databases for uaa and report services
You need to be authorized as DB admin
Creating uaa database
You may consider changing the at least password for the uaa user.
CREATE DATABASE uaa TEMPLATE template0 ENCODING 'utf8' LC_COLLATE = 'en_US.UTF-8' LC_CTYPE = 'en_US.UTF-8';
CREATE USER uaa with encrypted password 'PaSSw0rd';
GRANT ALL PRIVILEGES ON database uaa to uaa;
Creating report database
You may consider changing the at least password for the report user.
CREATE DATABASE report TEMPLATE template0 ENCODING 'utf8' LC_COLLATE = 'en_US.UTF-8' LC_CTYPE = 'en_US.UTF-8';
CREATE USER report with encrypted password 'PaSSw0rd';
GRANT ALL PRIVILEGES ON database report to report;
By default Allure Testops uses public database schema.
PostgreSQL 15 requires explicit granting the public schema permission to uaa and report database users
GRANT ALL ON SCHEMA public TO report;
GRANT ALL ON SCHEMA public TO uaa;