A cautionary tale of names

[roger peppe]

On 12 January 2015 at 15:43, Gustavo Niemeyer <gustavo at niemeyer.net> wrote:
> A few quick notes:
>
> - Having an understandable name in a resource useful

It's also good to be clear about what a name actually signifies.

Currently (unless things have changed since I last looked)
it's entirely possible to start an environment with one name,
then send the resulting .jenv file to someone else, who can
store it under some other name and still access the environment
under the different name.

Local aliases/names are nice - no worry about global name space
clashes.

But I agree that meaningful resource names are useful too.

One possibility is that the UUID could incorporate the original
environment name (I guess it would technically no longer be
a UUID then, but UUID standards are overrated IMHO).

Another possibility is to provide some other way to give
a name at environment bootstrap time (e.g. a config option)
that would be associated with resources created by the environment.

  cheers,
    rog.