Skip to content

Commit e3369c9

Browse files
authored
Merge pull request #190384 from tfitzmac/0302depends
clarify dependencies
2 parents f1743f1 + 484c6ef commit e3369c9

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

articles/azure-resource-manager/bicep/resource-dependencies.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Set resource dependencies in Bicep
33
description: Describes how to specify the order resources are deployed.
44
ms.topic: conceptual
5-
ms.date: 02/04/2022
5+
ms.date: 03/02/2022
66
---
77

88
# Resource dependencies in Bicep
@@ -69,7 +69,7 @@ resource otherZone 'Microsoft.Network/dnszones@2018-05-01' = {
6969
}
7070
```
7171

72-
While you may be inclined to use `dependsOn` to map relationships between your resources, it's important to understand why you're doing it. For example, to document how resources are interconnected, `dependsOn` isn't the right approach. You can't query which resources were defined in the `dependsOn` element after deployment. Setting unnecessary dependencies slows deployment time because Resource Manager can't deploy those resources in parallel.
72+
While you may be inclined to use `dependsOn` to map relationships between your resources, it's important to understand why you're doing it. For example, to document how resources are interconnected, `dependsOn` isn't the right approach. After deployment, the resource doesn't retain deployment dependencies in its properties, so there are no commands or operations that let you see dependencies. Setting unnecessary dependencies slows deployment time because Resource Manager can't deploy those resources in parallel.
7373

7474
Even though explicit dependencies are sometimes required, the need for them is rare. In most cases, you can use a symbolic name to imply the dependency between resources. If you find yourself setting explicit dependencies, you should consider if there's a way to remove it.
7575

articles/azure-resource-manager/templates/resource-dependency.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Set deployment order for resources
33
description: Describes how to set one Azure resource as dependent on another resource during deployment. The dependencies ensure resources are deployed in the correct order.
44
ms.topic: conceptual
5-
ms.date: 12/21/2020
5+
ms.date: 03/02/2022
66
---
77

88
# Define the order for deploying resources in ARM templates
@@ -32,7 +32,7 @@ The following example shows a network interface that depends on a virtual networ
3232
}
3333
```
3434

35-
While you may be inclined to use `dependsOn` to map relationships between your resources, it's important to understand why you're doing it. For example, to document how resources are interconnected, `dependsOn` isn't the right approach. You can't query which resources were defined in the `dependsOn` element after deployment. Setting unnecessary dependencies slows deployment time because Resource Manager can't deploy those resources in parallel.
35+
While you may be inclined to use `dependsOn` to map relationships between your resources, it's important to understand why you're doing it. For example, to document how resources are interconnected, `dependsOn` isn't the right approach. After deployment, the resource doesn't retain deployment dependencies in its properties, so there are no commands or operations that let you see dependencies. Setting unnecessary dependencies slows deployment time because Resource Manager can't deploy those resources in parallel.
3636

3737
## Child resources
3838

0 commit comments

Comments
 (0)