Comment 9 for bug 1381136

Zane, regarding the first part of comment #8: 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 would be surprised by a system that has the same resource ID on two different resources (e.g., a stack and also a resource contained in that stack).

This connects to the bigger picture here, which I now see I did not describe clearly enough at the beginning. The problem is not that I am personally surprised by the output of {get_resource: somestack}. The problem is that a template author has no way to refer to a stack, in places where reference is done by resource ID. The first place I noticed this is for OS::Heat::HARestarter, which takes a resource ID for the resource that is the head of sub-graph to delete and re-create. The second place this has come up is in the proposal to add a list of members-to-delete to as an optional property of a scaling group; part of the design problem there is to decide how the members to be deleted should be identified.