Comment 4 for bug 1936467

I think what we are misinterpreting what we saw when sql_connection was moved into the [database] section. When sql_connection was in the DEFAULT section the parameter was picked up and for some reason yet to be determined the connection fails. When the sql_connection is moved into the [database] section it fails to be picked up at all and for some reason the barbican worker does not error, I assume because it drops back to sqllite. Basically moving sql_connection parameter into the database section is the equivalent of commenting it out.

 I validated this by:
1) Having a valid sql_connection string in the default section of the config and confirming there was a corresponding connection in the mysql db.
2) Moved the sql_connection into the [database] section and confirmed the barbican-worker started fine but there was no connection in the mysql db.