Comment 1 for bug 1680021

The problem isn't that this is a nested stack, the problem is that ResourceChain uses non-descriptive resource names like "3". (Changing that now would massively bork existing stacks though.)

It _might_ be possible to hack the error messages for just ResourceChain to display e.g. the type name instead of the resource name in the error path.

> perhaps setting concurrent: false so the resource names match the input list indexes.

This seems wrong - the indices are always assigned in the same order as the input list. The only difference that concurrent: false makes is that adds depends_on to order the actual creation.