cli should not be dependent on a specific directory structure

[corysimmons]

To run $ hasura console I've needed to have a config.yaml present.

It only had the graphql endpoint in it.

If I delete this file $ hasura console fails.

If I delete this file and use the --endpoint flag (effectively replacing the only data config.yaml was providing), $ hasura console still fails. I'd expect it to work.

My use-case is wanting to do something like $ yarn dev:staging and $ yarn dev:production where these scripts just have different --endpoints.

[letientai299]

My issue (#2039) is closed as duplicated to this one, so I will plug my suggestion here.

• Beside flag --endpoint, we can also have flag --admin-secret, and that will free us from config.yaml completely.

• The folder migration is not needed for following commands:

  • metadata version
  • metadata clear
  • metadata export (the folders can be created on the fly)
  • console (with the help of 2 new flags)

[HarryVasanth]

My issue (#2039) is closed as duplicated to this one, so I will plug my suggestion here.

• Beside flag --endpoint, we can also have flag --admin-secret, and that will free us from config.yaml completely.

• The folder migration is not needed for following commands:

  • metadata version
  • metadata clear
  • metadata export (the folders can be created on the fly)
  • console (with the help of 2 new flags)

Did you manage to find a workaround for this @letientai299?