feat: allow external postgres to be used by debezium plugin

[davidlopezre]

This PR changes the readiness command to allow the Debezium server plugin to use a postgres outside of the devbox virtual environment.

[jay-aye-see-kay]

The change seems reasonable, just wanted to understand the naming of env vars in that plugin.

The common pattern I’ve seen in the past is setting PGHOST PGPORT PGUSER etc for the project and all cli tools will pick up on those without having to set flags.

But in this plugin we use DB_* env vars which don’t get picked up automatically (by anything know of). Is this intentional to prevent conflicts outside the plugin?

[m-dwyer]

The change seems reasonable, just wanted to understand the naming of env vars in that plugin.

The common pattern I’ve seen in the past is setting PGHOST PGPORT PGUSER etc for the project and all cli tools will pick up on those without having to set flags.

But in this plugin we use DB_* env vars which don’t get picked up automatically (by anything know of). Is this intentional to prevent conflicts outside the plugin?

Good call out.

The reason we settled on DB_* is because we envisage the possibility of extending the debezium server plugin.

At the moment, it just contains a static config file that uses the PostgresConnector and implements the Outbox pattern, but there may be a point where we extend out the functionality to Mongo or another DBMS, allowing us to have a consistent way for implementing local CDC across different databases.