[FEATURE]: Async Configuration

[shellscape]

Describe what you want

At present drizzle has a traditional constructor/initializer with literal configuration properties. e.g.

const pool = new Pool({ connectionString: process.env.DB_URL! });
drizzle(pool, { schema })

Now consider that our DB Url is located in a secret manager/store, which requires an async request to fetch.

const dbUrl = await getRemoteSecret('DB_URL');
const pool = new Pool({ connectionString: dbUrl });
drizzle(pool, { schema })

In ES module land, this works without issue. However, in Node-CJS land this does not work. Our only alternative is to export an async init method and use that wherever we'd like to access our database. That is quite common and normal for folks who are still working in CJS. There is a pattern that could be used to alleviate the need for an async init method - allowing for asyn configuration. Bundlers like Vite, Webpack, and Rollup all support async configs for this kind of purpose, so there is some prior art there. One such implementation might look like:

drizzle(async () => {
 const dbUrl = await getRemoteSecret('DB_URL');
 const pool = new Pool({ connectionString: dbUrl });

 return { client: pool, schema };
})

Given how the result of drizzle is typically used, that might require some fancy use of Proxy.

I noticed there were a few other issues open about top-level await and an older reverted commit which might be solved by this approach.

[jmls]

does anyone have an idea on how to implement this ? I need to configure the db host based on an async call

[jbeckermanthrotle]

We're having the same exact issue! We've coded a work around, but it is not ideal and makes the app extremely slow. Is there a plan to allow for Async calls to inject our credentials like requested above?

[MDrooker]

Any update on the thinking for this feature?