On Mon, Nov 20, 2023 at 4:14 PM Jonathan Vanasco wrote:
>
> SQLAlchemy supports this via `Engine.dispose()`, which is the documented way
> of handling a post-fork connection:
>
>https://docs.sqlalchemy.org/en/13/core/connections.html#engine-disposal
Yes, that sounds familiar.
--
You
100% agree with Michael's comments about signed headers. When dealing with
credentials, a lot of people distrust proxies and testing them - so on top
of removing all headers, anything added will be signed (or the aggregate
signed) with a low-cost method, which can easily be tested.
On
SQLAlchemy supports this via `Engine.dispose()`, which is the documented
way of handling a post-fork connection:
https://docs.sqlalchemy.org/en/13/core/connections.html#engine-disposal
Invoking `Pool.recreate()` should be fine, but the documented pattern is to
call `Engine.dispose`
> How
