Add support for running a command to get the database connection string in postgrestools.jsonc

[remorses]

I want to use the Supabase database directly instead of a local database, to do that you could add support for a config option dbCommand to get the database uri via stdout

{
  "$schema": "./docs/schemas/latest/schema.json",
  // get the database uri using dotenv-cli npm package
  "dbCommand": "dotenv -- bash -c 'echo $DATABASE_URL'",
  // get database uri using doppler
  "dbCommand": "doppler secrets get --plain DATABASE_URL",
}

This allows to get the database url using tools like Doppler or dotenv

[psteinroe]

Thanks for the suggestion!

Out of curiosity: why do you want to connect directly to the remote database? Latencies will be higher.

[remorses]

Latency shouldn’t be a big issue, I prefer using a remote database to make local setup easier

[mdeville]

It might be useful even in "local" contexts.
For instance we have a workstation which is shared by many users with one DB for each user.
The connection to each local DB is provided behind an environment variable (like so: $DEV_DB_URI).
Being able to get the URI without writing it directly in the postgrestools.jsonc file would allow us to commit the config file for everyone.

[psteinroe]

Makes total sense! Will add an issue for this 🫶🏼