Support BOSH_DEPLOYMENT, BOSH_ENVIRONMENT

[dpb587]

Generically, for things like .envrc...

$ cd workspace/cf-release
direnv: loading .envrc
direnv: export +BOSH_DEPLOYMENT +BOSH_ENVIRONMENT

$ cat .envrc
export BOSH_ENVIRONMENT="$(hostname)"
export BOSH_DEPLOYMENT="$(basename "$PWD")"

$ bosh ssh mysql
Using environment 'https://lake:25555' as user 'admin'

Using deployment 'cf-release'
...

What do you think?

[cfdreddbot]

Hey dpb587!

Thanks for submitting this pull request! I'm here to inform the recipients of the pull request that you and the commit authors have already signed the CLA.

[cppforlife]

@dpb587 i like it! though we already added BOSH_ENVIRONMENT, mind changing commit to only do BOSH_DEPLOYMENT?

[voelzmo]

Just as a side comment: Usually deployment names don't have the -release, i.e. it is called cf, not cf-release: https://github.com/cloudfoundry/cf-release/blob/master/example_manifests/minimal-aws.yml#L4 And I guess it is even worse than I thought with the bosh-lite deployment being named cf-warden

So using the directory name sounds interesting, but will lead to something entirely different than what people do today.

[cppforlife]

@voelzmo that's just an example. .envrc would be in your repo so you can hard code it to whatever you want (i would recommend hardcoding it). cli change is only BOSH_DEPLOYMENT env.

[dpb587]

Rebased/changed. Yeah, cf-release was an odd example; oops.