Use fully qualified symbolic name to refer to copy loop in dependsOn #16236
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.
Resolves #16230
#15910 updated copy loops on nested resources to use the fully qualified symbolic name of the resource as the copy loop name in order to fix a language version 2.0 breaking change (since lv 2.0 blocks duplicate copy loop names). However, that PR did not update how
dependsOn
is emitted in non-symbolic name templates (where a dependency on all members of a looped resource is expressed as a dependency on the copy loop name).Microsoft Reviewers: Open in CodeFlow