Reviewers: mp+212960_code.launchpad.net, Message: Please take a look. Description: Have destroy-environment handle empty .jenv file Have a particular error raised for empty environment files, that we get when there is an emtpy .jenv file. If we have an empty file, we currently get this output: tim@jake:~$ touch .juju/environments/testlocal.jenv tim@jake:~$ juju status ERROR Unable to connect to environment "testlocal". Please check your credentials or use 'juju bootstrap' to create a new environment. Error details: environment is not bootstrapped tim@jake:~$ juju bootstrap WARNING ignoring environments.yaml: using bootstrap config in file "/home/tim/.juju/environments/testlocal.jenv" ERROR environment has no bootstrap configuration data I think this is reasonable, however we also used to get the error when trying to destroy the environment. Now we get this: tim@jake:~$ juju destroy-environment -y testlocal removing empty environment file https://code.launchpad.net/~thumper/juju-core/error-on-empty-jenv-file/+merge/212960 (do not edit description out of merge proposal) Please review this at https://codereview.appspot.com/80950044/ Affected files (+29, -1 lines): A [revision details] M cmd/juju/destroyenvironment.go M cmd/juju/destroyenvironment_test.go M environs/open.go Index: [revision details] === added file '[revision details]' --- [revision details] 2012-01-01 00:00:00 +0000 +++ [revision details] 2012-01-01 00:00:00 +0000 @@ -0,0 +1,2 @@ +Old revision: tarmac-20140326171935-rwmkmlytkkvq26d6 +New revision: