Fix allow copy resources to have same name #1300
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Summary
Unroll loops while resource invocation order is being determined. This means that resources still need to have a unique name+type combination, however, a copy loop is treated as a collection of same resource (meaning same name) which is allowed. So you can't explicitly have more than one resource with same name+type, but a copy resource is allowed to have a single name for every instance in the copy.
This also required making a previous private function public.
PR Context
Fix #1270