1.3.3.3 Network Controller dependent resources
This section provides a complete list of all the dependencies between resources and how concurrent operations are handled. In addition, the sections on each resource provides its dependency information.
Read-only elements that are a resourceRef to a different resource will indicate that the resource has a different resource that has taken a dependency on it (for example, GatewayPools has a read-only resourceRef to one or more gateways resources).
There are 4 scenarios that are relevant for concurrent operations when there are dependent resources.
DELETE descendant resource: When a DELETE operation is performed on a descendant resource while its property.provisioningState is in the Updating, Deleting, or Failed state, that the DELETE operation will be processed.
PUT descendant resource: When a PUT operation is performed on a descendant resource while its property.provisioningState is in the Updating, Deleting, or Failed state, the PUT operation returns an HTTP code 409 (Conflict) response. See the error code section in each resource for error response content details.
DELETE dependent resource: When a DELETE operation is performed on a dependent resource that has resources depending on it, the DELETE operation will return an HTTP code 409 (Conflict) response. See the error code section in each resource for error response content details.
PUT dependent resource: When a PUT operation is performed on a resource while there are dependent resources, the PUT operation will be processed.