Connect to multiple databases and controlling the user list directly

[TimSC]

For connecting to multiple databases and controlling the user list directly, the DB_DATABASES and AUTH_USERLIST env variables may be used.

docker run -e DB_DATABASES='flask = host = 192.168.1.5 port=5432 user=web_user password=xxxx dbname=flask,data_web = host = 192.168.1.10 port=5432 user=web_user password=xxxxx dbname=data_web' -e LISTEN_PORT=5439 -p 5439:5439 -e AUTH_USERLIST="\"username1\" \"password\",\"username2\" \"password2\"" pgbouncer

[jheld]

Would love to have this support merged.

[homme]

It would be nice if this extended the current DATABASE_URL idiom to allow multiple URLs, e.g. by setting DATABASE_URLS. At the moment it's limited to the postgres specific DSN format.

[jflambert]

Hi @homme I see what you mean. However DATABASE_URL itself is limiting in that it doesn't let you override some global pgbouncer configs such as auth_user, auth_query, auth_dbname, etc. Please correct me if I'm wrong! Either way please feel free to open a second issue.

@TimSC I'm sorry it took me close to 3 years before evaluating this PR but I think I like your approach. I'm just trying to understand the relationship between DB_DATABASES and AUTH_USERLIST. Right now we add an entry to userlist.txt from user/pass vars. I wonder if some users would expect us to automatically parse the user/pass from each DB_DATABASES entry if AUTH_USERLIST is not provided.