Like I said, what get_resource (equivalent to "Ref" in CFN templates) returns is dependent on the resource, not the template DSL you use so there is no "hot inantation" of an AWS resource.
So what I think you are saying is that there's a bug in provider resources (which are *not* AWS Stack resources), e.g template resource GetRefId has a bug here:
Mike: If you're talking about the AWS stack resource, then returning an ARN is not unexpected:
http:// docs.aws. amazon. com/AWSCloudFor mation/ latest/ UserGuide/ aws-properties- stack.html
Like I said, what get_resource (equivalent to "Ref" in CFN templates) returns is dependent on the resource, not the template DSL you use so there is no "hot inantation" of an AWS resource.
So what I think you are saying is that there's a bug in provider resources (which are *not* AWS Stack resources), e.g template resource GetRefId has a bug here:
https:/ /github. com/openstack/ heat/blob/ master/ heat/engine/ resources/ template_ resource. py#L270
That is a bug, this (in the AWS Stack resource) is not:
https:/ /github. com/openstack/ heat/blob/ master/ heat/engine/ resources/ stack.py# L95