/kind bug

What happened:

When initializing a new ksonnet app, an initial registry cache for incubator is created with the following path:

$ tree .ksonnet/
.ksonnet/
└── registries
    └── incubator
        └── 40285d8a14f1ac5787e405e1023cf0c07f6aa28c.yaml

Running a subsequent registry command, e.g. ks describe incubator, will create a cache with a different path:

$ ks registry describe incubator
...

$ tree .ksonnet/
.ksonnet/
└── registries
    ├── 40285d8a14f1ac5787e405e1023cf0c07f6aa28c.yaml
    └── incubator
        └── 40285d8a14f1ac5787e405e1023cf0c07f6aa28c.yaml

What you expected to happen:

Regisry cache paths should be consistent between app initialization and subsequent registry operations.

How to reproduce it (as minimally and precisely as possible):

ks init example && cd example
ks registry describe incubator
tree .ksonnet/

Anything else we need to know?:

Environment:

• ksonnet version (use ks version): 0.11.0
• Kubernetes version (use kubectl version): version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.0", GitCommit:"fc32d2f3698e36b93322a3465f63a14e9f0eaead", GitTreeState:"clean", BuildDate:"2018-03-26T16:44:10Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}