Update managedDisks-customimagevm.json to avoid loops depending on loops #742
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.
The Deployment Engine processes each resource in a loop as if it depended on every resource in the previous loop iteration. This information is exposed on a deployment GET request via
properties.dependencies
, which contains a lot of data. The amount of data returned by this request is proportional toloop_size^2
as a result of this authoring pattern, which can result in huge amounts of data and slow performance for users with large loop counts.