Open sangee2004 opened 9 months ago
Changing the DB name is not really a supported use case. You end up creating orphaned databases that will get deleted when you remove the acorn.
There was a bug however, so the @{DB_NAME} should now be whatever the correct value is.
@cloudnautique In this use case , i am not updating an existing service with a different DB name. I am creating a new service with same clusterName and dbUser(as existing service) but different dbName which results in the existing service to have DB connection errors.
This should be resolved now. A username is generated based on the Acorn and Project names.
Steps to reproduce the problem:
app1
acorn run -n app1 . --clusterName santest1 --dbName test1 --dbUser testusernew --provider AWS --region US_WEST_2
consumingapp1
forapp1
. Make sure consuming app is able to connect successfully to DB.app2
using the sameclusterName
anddbUser
but differentdbName
acorn run -n app2 . --clusterName santest1 --dbName test3 --dbUser testusernew --provider AWS --region US_WEST_2
consumingapp2
forapp2
. Make sure consuming app is able to connect successfully to DB. After this,Try to make a DB connection from
consumingapp1
(from step2). DB connection starts failing:From MongoDB console:
Notice that tbith he
admin
anduser
both get overwritten for DB name -test3