Comment 13 for bug 1381136

> was your vision that a template might output a resource ID that is the resource ID of one of the resources it contains, or a resource ID that the template synthesizes (e.g., by string munging or random string generation)?

I figured it would be an output, so the user could in principle do whatever they like, but the most common case would be to reference a resource ID from within the nested template. So e.g. you could specify in your environment file a mapping from OS::Nova::Server -> my_customised_server.yaml where you customise the server to e.g. add a port, or preset some common properties, or something. You'd then be able to use OS::Nova::Server in _exactly_ the same way as if you had not mapped it, because when you do {get_resource: } on it it would still return the physical resource ID of the server.