Setting all parts of connection for a tenant goes wrong

[psaulus]

Setting all parts of connection for a tenant goes wrong

[stancl]

There's a known bug in v3 where creating databases on another host (specified via either tenancy_db_host or tenancy_db_connection) doesn't know correctly and instead tries to create the database on the same database host as the central connection.

But still, even with all these parameters, the application shows me TenantDatabaseDoesNotExistException exception, because it looks for the database into default = central database. I've debugged that, and I see that even without set tenancy.template_tenant_connection config MySQLDatabaseManager and all connected abstracts operates on central set connection or could operate on the template if that would be set

This sounds similar to that.

In v4 we've solved this by introducing a new connection -- tenant_host_connection -- used for connecting to the proper database server per the tenant config. This is a wontfix in v3 since it'd require some breaking changes, and with v4 being close to release we prefer to not make any breaking changes in v3.

[stancl]

Are you using a pre-created database, or having tenancy create the database for you?

[psaulus]

I checked that CreateDatabase job from the package wasn't enough, so I've disabled it in the provider and replaced with my own, which creates a database. I've checked double time that database exists and all user and permissions are properly set.