DB and env related issues while upgrading existing instance to 3.0.0

Community Support
1

Hi everyone. I want to upgrade our existing instance to 3.0.0 and am facing several issues. None of the release notes ( DataGerry | Release 3.0.0 , Changelogs — DataGerry latest documentation ) mentions a breaking change in the config file and how environment variables are handled between 1.7.2 and 3.0.0

Right now I am passing following environment variables into the Docker Container:

- DATAGERRY_Database_host

  • DATAGERRY_Database_password
  • DATAGERRY_Database_username
  • DATAGERRY_MessageQueueing_host
  • DATAGERRY_MessageQueueing_password
  • DATAGERRY_MessageQueueing_username

I already found that RabbitMQ is not needed anymore.

By experimenting I found that the database related environment variables are not processed anymore, or at least don’t overwrite the defaults from /etc/datagerry/cmdb.conf. Am I missing something?

A second issue seems to be that I am not able to connect to a mongodb instance that requires authentication. Am I missing something?

Thanks in advance for your answers.

2

Figured it out by inspecting the codebase. I had to drop all above environment variables and just use CONNECTION_STRING environment variable, containing the mongodb connection string including authentication. :partying_face: