The CLI should accept any path provided by DEIS_PROFILE

[jchauncey]

Right now the json files can only exists in the .deis directory.

[bacongobbler]

Personally I'd rather deprecate DEIS_PROFILE in favor of a global --config-file flag to specify where to read config from, defaulting to ~/.deis/client.json

[jchauncey]

Yeah I actually like that better. Might try and add that soon.

[Joshua-Anderson]

I'm torn on this. I think that being able to pass a path is adds nice flexibility, but $DEIS_PROFILE fits a multi-cluster workflow really well.

Being able to export DEIS_PROFILE=staging or export DEIS_PROFILE=production is super quick and intuitive way to switch between multiple clusters.

[bacongobbler]

There's nothing stopping you from replicating the same behavior with --config-file. It just adds more flexibility for users. For example, here's a script to replicate the same behavior as $DEIS_PROFILE with --config-file:

#!/bin/bash

DEIS_PROFILE=${DEIS_PROFILE:-client}
deis --config-file "$HOME/.deis/$DEIS_PROFILE.json" $@

Users may also want to specify a global client config path to share one config across all users of a system (e.g. /etc/deis/client.json), which the client currently does not allow.

[jchauncey]

So I think keeping DEIS_PROFILE while accepting --config or --client-config is perfectly acceptable. I would just make the CLI option override the env var.

[sstarcher]

I think adding --client-config is a good idea, but any CLI flag like that should be backed by an environment variable or an additional command should be supported to set the client config long term.

Similar with K8S you can specify --kubeconfig or kubectl config or KUBE_something_something environment variable

[Joshua-Anderson]

My proposal is that:

1. $DEIS_PROFILE should support file-paths in addition to just a name.
2. A global flag called --config acts identically to $DEIS_PROFILE

[Joshua-Anderson]

A command line flag is going to be needed to run tests in parallel. Otherwise all tests have to share the same $DEIS_PROFILE, so I'm going to start work on this issue.