How to pass an SSL context to the postgresql backend?

[Lawouach]

Hi,

It appears that databases only accepts a boolean to indicate if you want to connect over TLS to postgresql. But, the asyncpg driver supports to pass your own context, which is necessary when you have your own certs.

This make integrating in some environment a showstopper (our environment relies on TLS internally).

Was there a specific issue for not allowing passing a context?

Cheers,

• Sylvain

[tomchristie]

See #71

[Lawouach]

This sounds like the good basis indeed.

[Lawouach]

Hi Tom,

Thanks for being so swift. However, looking at the code, I'm not sure I see how to provide a SSL context myself. It seems it still expects a boolean, right?

Or am I reading that one wrong?

[tomchristie]

You should be able to pass anything accepted by asyncpg.Connection() or asyncpg.create_pool.

• https://magicstack.github.io/asyncpg/current/api/index.html#connection
• https://magicstack.github.io/asyncpg/current/api/index.html#asyncpg.pool.create_pool

I believe ssl accepts either an SSLContext or a boolean.

[Lawouach]

Totally! I misread the code :)

Sorry. Thanks again for the speed :)