Comment 10 for bug 1381136

Sorry, that was maybe a little too sloppy. The problem is that a template author has no way to refer to a resource that is a nested stack, in places where reference is done by resource ID.

Concrete example 1:

resources:
  somestack:
    type: AWS::CloudFormation::Stack
    properties: {...stuff...}

  replacer:
    type: OS::Heat::HARestarter
    properties:
      InstanceID: {get_resource: somestack}

That does not work.

Concrete example 2:

resources:
  sg:
    type: OS::Heat::ResourceGroup
    properties:
      resource_def:
        type: Something.yaml
        properties: ...
      removal_policy:
        resource_id_list: [ ... the result of FnGetRefId of a member ... ]