Repository navigation
Replies: 3 comments 3 replies
|
personally i'd love if more tools standardized on |
3 replies
|
thanks for the feedback! We are tracking something similar in #302. adding this to the issue 👍🏼 |
0 replies
|
This is supported now: |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Problem
Currently there is a need to specify "db.password" to get proper information about the database. But as postgrestools.jsonc is committed to the repository, it should not contain any secrets, even local ones.
I tried to find a solution, but couldn't find one that works for me.
Excluding the password and passing it via cli argument works in cli-only settings, but setting cli arguments is not supported by the VSCode extension, it seems.
Suggestion
Therefore I would like to suggest the ability to use .env or environment variables to set connection details. This allows a lot of flexibility for everyone.
Example
{ // ... "db": { "host": "${POSTGRES_HOST}", "port": "${POSTGRES_PORT}", "username": "${POSTGRES_USERNAME}", "password": "${POSTGRES_PASSWORD}", // <-- prevents potential leak of passwords "database": "${POSTGRES_DATABASE}", // ... } }All reactions