Comment 12 for bug 1381136

> My original vision of TemplateResource was to allow the user to specify a special Output in their template to specify the resource ID

+100 - stevebaker and I were discussing this in the context of provider-resource abstracted SoftwareConfig resources recently, and IMO it's something we do need.

I don't think it's "same resource ID on two different resources" at all, merely giving some control to template authors who want to use provider resources for encapulation transparently. The resource has exactly one ID, as does the stack, you're just changing what get_resource references for template-author convenience.