Complex pgx configuration not supported
eleduardo opened this issue · 0 comments
Describe the feature
For some use cases (for example around TLS in dockerized dynamic environments) just setting up the pgx configuration from the dsn string or connection string is not enough.
Motivation
In the particular case I am running into I need to set up a TLS context but the certificates and key are not available in the file system but retrieved from a vault source (think AWS secret manager and others). In this environment the certificates cannot be written to the disk as they are running as docker containers from scratch and there are not permissions to write to the file system... even if there were I do not want to expose the certs and keys to a potential snoop.
I can think of other configuration sets where it would be better to just pass the pgx configuration directly and just have the adapter perform the connection