Azure / bicep-registry-modules

Bicep registry modules
MIT License
465 stars 308 forks source link

[AVM Module Issue]: Backend Address Pools on Load balancers do not have examples of how to add a backend address pool with backend IP configurations #3089

Open ronarieke opened 3 weeks ago

ronarieke commented 3 weeks ago

Check for previous/existing GitHub issues

Issue Type?

Bug

Module Name

avm/res/network/load-balancer

(Optional) Module Version

No response

Description

We find that deploying the load balancer using the example parameters for backendAddressPools results in a load balancer with no NICs attached, and want to see an example parameter for backendAddressPools that includes backendIPConfigurations with IP properties:

    backendAddressPools: [
      {
        name: backendPool1Name
        properties: {
          backendIPConfigurations: [
            {
              id: '${nic1Id}/ipConfigurations/ipconfig1'
            }
          ]
        }
      }
      {
        name: backendPool2Name
        properties: {
          backendIPConfigurations: [
            {
              id: '${nic2Id}/ipConfigurations/ipconfig1'
            }
          ]
        }
      }
    ]

My MSFT alias is ron.rieke@microsoft.com

(Optional) Correlation Id

No response

microsoft-github-policy-service[bot] commented 3 weeks ago

[!IMPORTANT] The "Needs: Triage :mag:" label must be removed once the triage process is complete!

[!TIP] For additional guidance on how to triage this issue/PR, see the BRM Issue Triage documentation.

avm-team-linter[bot] commented 3 weeks ago

@ronarieke, thanks for submitting this issue for the avm/res/network/load-balancer module!

[!IMPORTANT] A member of the @Azure/avm-res-network-loadbalancer-module-owners-bicep or @Azure/avm-res-network-loadbalancer-module-contributors-bicep team will review it soon!

microsoft-github-policy-service[bot] commented 2 weeks ago

[!WARNING] Tagging the AVM Core Team (@Azure/avm-core-team-technical-bicep) due to a module owner or contributor having not responded to this issue within 3 business days. The AVM Core Team will attempt to contact the module owners/contributors directly.

[!TIP]

  • To prevent further actions to take effect, the "Status: Response Overdue 🚩" label must be removed, once this issue has been responded to.
  • To avoid this rule being (re)triggered, the ""Needs: Triage :mag:" label must be removed as part of the triage process (when the issue is first responded to)!