Can't use GCP Cloud SQL connection string with native PostgresSettings

[rodrigoalmeida94]

When using GCP database instances with Cloud Run functions, the connection string of the database includes unix sockets, i.e.:

postgresql://cerulean-cloud-test-database:APASSWORD@/SOMEDB?host=/cloudsql/SOME-PROJECT:europe-west1:SOME-INSTANCE-af6e417

Passing this as DATABASE_URL returns a validation error coming from Pydantic.PostgresDsn -

tifeatures/tifeatures/settings.py

Line 71 in 257246a

return pydantic.PostgresDsn.build(

.
This has been discussed upstream and more recently here, and looks like this won't be addressed any time soon. Since MagicStack/asyncpg#419 AsyncPg supports these types of connection string.

The way I got around this now is defining my own PostgresSettings class, removing the pydantic validation all together. This is fine but I'm wondering if it could make sense to add an extra env var like TIFEATURES_CLOUDSQL which we could set to True, and then that would bypass the pydantic validation?

Thanks!

[vincentsarago]

Thanks for opening the issue @rodrigoalmeida94

This is fine but I'm wondering if it could make sense to add an extra env var like TIFEATURES_CLOUDSQL which we could set to True, and then that would bypass the pydantic validation?

I kinda don't really like adding something specific for Cloud provider use case, and would prefer if we can push the fix upstream or do like you do: customize your own application!

[rodrigoalmeida94]

Perfect, makes sense to me!