Comment 2 for bug 1719459

So while I agree there is workspace support and you can use the env vars to workaround this. I feel this is still a valid bug.

For a cli tool that verifies whether a config file works to not having support to pass in an arbitrary config file path with a cli flag is kinda weird. Especially for when you're creating a config file outside outside of a workspace or a dir named etc/. It's not unreasonable to assume that people want to pass a config file in from the cli.