[Feature] Support ENV of host, port, user, password, dbname

hasura / graphql-engine

Blazing fast, instant realtime GraphQL APIs on your DB with fine grained access control, also trigger webhooks on database events.

https://hasura.io

Apache License 2.0

31.08k stars 2.77k forks source link

[Feature] Support ENV of host, port, user, password, dbname #4782

Open ivawzh opened 4 years ago

ivawzh commented 4 years ago

Hi Hasura. Congrats on your great work designing and maintaining Hasura.

I am wondering if there is a current way to support taking ENV of database host, port, user, password, and dbname; instead of HASURA_GRAPHQL_DATABASE_URL?

I am asking because AWS CDK doesn't have a way to support joining plaintexts from a shared secret at ECS task create time. And I believe supporting separate ENV instead of URL is also easing param management in general.

fo-fo commented 3 years ago

This would be a very welcome change. Note also that there might be dynamic parts in the database URL (e.g., the database endpoint address), in which case the full database URL cannot be stored as a secret.

chrisknu commented 1 year ago

Curious to know if there has been any traction on this point