Updating configuration for release 25.3.2
In the release 25.3.2 we added a new feature allowing the usage AWS SQS as a message broker for Allure TestOps.
The change requires updating the configuration parameters as follows:
For the docker compose configuration template file (docker-compose.yml) it's required to add a default parameter to the SPRING_PROFILES_ACTIVE variable as follows:
As is
SPRING_PROFILES_ACTIVE: compose
to be
SPRING_PROFILES_ACTIVE: "compose,rabbitmq"
Then service needs to be upgraded to the 25.3.2 release.
Helm chart version 5.25.0 has all required profiles defined for the upgrade.
Before upgrading, please check values.yaml for changes, then upgrade application to 25.3.2 as usual.
The configuration file of Allure TestOps residing here /opt/testops/conf/testops.conf needs to be updated as follows.
As is
SPRING_PROFILES_ACTIVE=package
to be
SPRING_PROFILES_ACTIVE="package,rabbitmq"
Then service needs to be upgraded to the 25.3.2 release.
What would happen if the configuration is not updated
If the profiles are not configured correctly as described above, the application will fail to start and will throw the following exception:
org.springframework.amqp.rabbit.support.ListenerExecutionFailedException: Listener method 'public void io.qameta.ato.rabbit.listener.UploadEventListener.onPostProcess(io.qameta.ato.common.event.UploadPostProcessEvent)' threw exception
at ...
<many-many lines and finally:>
at java.base/java.lang.Thread.run(Thread.java:1583)
Caused by: java.lang.NullPointerException: null
