Use d1 databse id from environment variables?

[az-nextsec]

What is the recommended way to make it so database_id is a variable (e.g. from .env or .dev.vars).

I want all my npx wrangler d1 command to see the same persistent d1 id both local and remote, but I want to treat it as a secret so that it doesn’t become a part of my codebase.

[jamesopstad]

Hi @az-nextsec. There's not a straightforward way to do this. In the future we will likely support programmatic config so that values can be read from process.env. I'm curious why you want to treat the database_id as a secret? They are not sensitive and can be included directly in the config.

[penalosa]

We haven't heard from you in while so I'm going to close this issue for now. If you're still running into problems feel free to open a new issue with more details and we can investigate further.