Allow passing SSL configuration into options for @key/postgres

I recently found that I was unable to use the keyv postgres backend because the production database I was connecting to forces SSL connections. This is a request to add the ability to pass SSL configuration options into the Keyv object. Or more generally to allow passing external pool for Keyv to make use of.

These are a sample of the errors I was getting:

Error from keyv.Keyv: error: no pg_hba.conf entry for host "3.89.49.50", user "postgres", database "postgres", SSL off

And the more cryptic message (this occurs after the above error):

TypeError: query is not a function
  File "/app/node_modules/@keyv/postgres/src/index.js", line 29, col 19, in <anonymous>
    .then(query => query(sqlString, values));
  File "/app/node_modules/@keyv/postgres/src/index.js", in runMicrotasks
  File "node:internal/process/task_queues", line 96, col 5, in processTicksAndRejections

Here’s a sample from my project of the SSL options:

import * as fs from 'fs';
import { Pool, PoolConfig } from 'pg';

function setupPgPool(): Pool {
  const poolConfig: PoolConfig = {
    connectionString:
      process.env.DATABASE_URL ||
      'postgres://postgres:postgres@localhost:5432/regen_registry',
  };

  if (process.env.NODE_ENV === 'production') {
    poolConfig.ssl = {
      ca: fs.readFileSync(`${__dirname}/../config/rds-combined-ca-bundle.pem`),
    };
  }

  const pool = new Pool(poolConfig);
  return pool;
}

const pgPool = setupPgPool();

export { pgPool };

Here’s an upstream issue with some additional info in case it is helpful. I would be glad to work on this once an approach is decided.

[jaredwray]

@wgwz - this should be going out in the next two weeks. Closing down this ticket.

[jaredwray]

The first approach where we pass the config into @keyv/postgres storage adapter would be the preferred.