add hasura cli arg to specify config.yaml config file path

[ilovett]

Allow specifying where the config.yaml is so the command can be run from anywhere

[manasag]

Hi @ilovett , thanks for opening this issue.

As per this doc, one can provide a custom env file which can act an alternative to a custom config file. e.g. hasura console --envfile production.env. Other option is the --project flag, where you can provide a "non current" project directory location.

Would the above options help in your use-case?

Also the request for custom config file seems to be duplicate of this #4561