No way to set `ssl: { rejectUnauthorized: false }` on the underlying knex connection?

[robcresswell]

Is there a way to pass through more options to the underlying knex config? sidequest seems to enforce a string and not allow any other options, even though knex / node-pg allow objects with other config.

[GiovaniGuizzo]

You can pass any Knex config object to the backend.

[robcresswell]

In what structure? Could you provide an example?

This does not seem to work, for me.

const dbConfig = {
  driver: '@sidequest/postgres-backend',
  config: {
    host: pgHost,
    port: 5432,
    user: pgUser,
    database: pgDatabase,
    password: pgPassword,
    ssl: pgSsl === 'true' ? { rejectUnauthorized: false } : false,
  },
};

await Sidequest.start({
  backend: dbConfig,
  jobPollingInterval: 1000,
});

But this does:

const dbConfig = {
  driver: '@sidequest/postgres-backend',
  config: `postgresql://${pgUser}:${pgPassword}@${pgHost}/${pgDatabase}${pgSsl === 'true' ? '?sslmode=require' : ''}`
};

await Sidequest.start({
  backend: dbConfig,
  jobPollingInterval: 1000,
});

[GiovaniGuizzo]

Yes, like that: https://docs.sidequestjs.com/engine/backends#postgresql-recommended

[robcresswell]

Yeah that just results in errors for me with identical config values. Unsure why the object fails.

[GiovaniGuizzo]

What is the error you are facing?