Azure / Azure/Azure-Landing-Zones

service_endpoints no longer supported in avm-res-network-virtualnetwork 0.16.0

Open
#554 6 comments 8 reactions 2 assignees Claimed by @Y1ngJ1eChen View on GitHub
Product: Terraform (AVM) Topic: Networking (general) :globe_with_meridians: Transfer From: TF avm-ptn-lz-vend :arrow_right:
Dominant language
PowerShell
Stars
96
Forks
70
Avg merge
3d 1h
Merged PRs (30d)
7

Description

### Check for previous/existing GitHub issues

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

### Issue Type?

I'm not sure

### (Optional) Module Version

0.1.0

### (Optional) Correlation Id

_No response_

### Description

First of all, thanks for the great work on the AVM modules.
While updating to avm-ptn-alz-sub-vending v0.1.0, I noticed one detail that might need attention.

In our configuration, the subnets are defined using the property:
```
service_endpoints = optional(set(string))
```
However, in avm-res-network-virtualnetwork this input has been updated and now expects:

```
service_endpoints_with_location = optional(list(object({
service = string
locations = optional(list(string), ["*"])
})))
```

As a result, our existing subnet definitions are no longer compatible with the module.

Please update alz-sub-vending to align with the updated VNet module, or provide guidance on how to correctly map the previous service_endpoints structure to the new service_endpoints_with_location format.

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.