Graphql-engine: docs: add top level entry on configuring hasura CLI with admin secret

Created on 9 Mar 2019  路  3Comments  路  Source: hasura/graphql-engine

Many different ways of doing it right?

  1. .env file
  2. --admin-secret flag
  3. config.yaml entry, but this is not good for version control
  4. env var on bash, export or prepend to command

@shahidhk I couldn't find a quick reference in the docs.

docs quickfix high
Source
picture coco98

Most helpful comment

Would be nice if you could load vars from .env in config.yaml, e.g.

# config.yaml (checked in to git repo)
endpoint: https://xxxxxxxx
admin_secret: ${HASURA_ADMIN_SECRET}

# .env (not in git repo)
HASURA_ADMIN_SECRET=xxxxxxxxxxxxxxx
picture r-moore on 16 Aug 2019
👍5

All 3 comments

.env is not supported. We can add the other docs soon.

shahidhk picture shahidhk on 11 Mar 2019

Would be nice if you could load vars from .env in config.yaml, e.g.

# config.yaml (checked in to git repo)
endpoint: https://xxxxxxxx
admin_secret: ${HASURA_ADMIN_SECRET}

# .env (not in git repo)
HASURA_ADMIN_SECRET=xxxxxxxxxxxxxxx
r-moore picture r-moore on 16 Aug 2019
👍5

This has been documented here.

marionschleifer picture marionschleifer on 8 Dec 2020
Was this page helpful?
0 / 5 - 0 ratings

Related issues

shahidhk picture shahidhk  路  3Comments
hooopo picture hooopo  路  3Comments
codepunkt picture codepunkt  路  3Comments
marionschleifer picture marionschleifer  路  3Comments
revskill10 picture revskill10  路  3Comments