Azure / Azure/bicep-registry-modules

[AVM Module Issue]: VNet peering local vs remote creation order

Open
#6,556 9 comments 0 reactions 1 assignee Claimed by @mjrich19 View on GitHub
Class: Resource Module :package: Type: AVM :a: :v: :m: Type: Feature Request :heavy_plus_sign:
Dominant language
Bicep
Stars
736
Forks
564
Avg merge
3d 15h
Merged PRs (30d)
30

Description

### Check for previous/existing GitHub issues

- [x] I have checked for previous/existing GitHub issues

### Issue Type?

Feature Request

### Module Name

avm/res/network/virtual-network

### (Optional) Module Version

0.7

### Description

The local peering shuold depend on remote.

In scenarios where an environment is repeatedly destroyed and re-created. For example a sandbox used to test IaC and if the environment contains peerings to a network which is outside the destroyed environment (hub network) the remote peering is left in disconnected state. Re-creating the destroyed environment and it's network with peerings fails unless the remote peering is re-created before the local peering. That way the remote peering goes to initiated state and creating the local peering succeeds.

Currently the remote peering doesn't have time to become initated before the local peering is created and ends up in failure.

### (Optional) Correlation Id

_No response_

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.