Excellent, I’ll test with the below. Thanks for the advice!
On Fri, May 22, 2020 at 8:18 PM Mike Bayer wrote:
> engine strategies are gone in 1.4 so you're going to want to make use of
> event and plugin hooks such as:
>
>
> https://docs.sqlalchemy.org/en/13/core/connections.html?highlight=plugi
engine strategies are gone in 1.4 so you're going to want to make use of event
and plugin hooks such as:
https://docs.sqlalchemy.org/en/13/core/connections.html?highlight=plugin#sqlalchemy.engine.CreateEnginePlugin
https://docs.sqlalchemy.org/en/13/core/events.html?highlight=do_connect#sqlalchem
For reference, we've used this engine strategy for a while, which seems to
get the job done. We're strictly on Postgres so the code could do with some
alterations to make it compatible with multiple backends, that's left as an
exercise to the reader :-)
The main work is done in _rds_engine_creator
You can modify how the engine makes connections using the do_connect event hook:
https://docs.sqlalchemy.org/en/13/core/events.html?highlight=do_connect#sqlalchemy.events.DialectEvents.do_connect
each time the engine/ pool go to make a new connection, you can affect all the
arguments here, or re
Hi,
I am looking to use credentials provided by the above functionality from
AWS. Basically, using either of these methods, you can obtain temporary
credentials (for RDS, just password, and Redshift both username and
password) that can be used to access the database. However, for long
running proc
