Must-share information (formatted with Markdown):
- which versions are you using (SonarQube, Scanner, Plugin, and any relevant extension)
SonarQube Developer Edition 10.2.0.77647
- how is SonarQube deployed: zip, Docker, Helm
- what are you trying to achieve
I have a SonarQube that connects to database endpoint.
The database endpoint is shared by two databases that run as master and replica. This endpoint works like pgpool.
In the sonar config (sonar.properties) in the SONAR_JDBC_URL section I have this database endpoint.
Now I would like to migrate instance running master and slave databases to another environment. This migration will change IP address and FQDN of the servers running master and slave databases but NOT change/modify SONAR_JDBC_URL.
I wanted to confirm that existing license key will not change after migration and there will be no need to re-generate the license key?
Welcome to the community!
How do the IP and FQDN of the DB change without changing the URL SonarQube uses to connect to the DB?
At any rate, the license key is based in part on your DB URL, so if that changes, then you’ll need a new key.
SonarQube 10.3 included a 7-day ‘grace period’ feature (you have to click a button to turn it on, BTW) when your license is invalidated because of a DB URL change. So before you do anything, I would upgrade SonarQube to the current version, which is now 10.4.
That way even if your
SONAR_JDBC_URL does change, you’ll have 7 days to get the new license key issued.
Thank you for your answer. I’ll schedule a sonar update then.
“How do the IP and FQDN of the DB change without changing the URL SonarQube uses to connect to the DB?”
It works like a load balancer - we have an endpoint to connect and the backend is configured to connect to the master and slave DB.