The bootstrap didn't fail - it did create a working .jenv.
You are correct, "juju destroy-environment" results in the following error:
ERROR null provider destruction is not implemented yet
The point I'm trying to make is that the implementation of "destroy-environment" for the null provider should be to remove the .jenv entry in all cases.
"destroy-environment" should do what it says on the can - destroy :) In the case of the null provider, there's nothing else to destroy than the .jenv entry...
Sidenote: Why would people pass .jenv files around? I don't see a usecase for that.
The bootstrap didn't fail - it did create a working .jenv.
You are correct, "juju destroy- environment" results in the following error:
ERROR null provider destruction is not implemented yet
The point I'm trying to make is that the implementation of "destroy- environment" for the null provider should be to remove the .jenv entry in all cases. environment" should do what it says on the can - destroy :) In the case of the null provider, there's nothing else to destroy than the .jenv entry...
"destroy-
Sidenote: Why would people pass .jenv files around? I don't see a usecase for that.