-
Notifications
You must be signed in to change notification settings - Fork 377
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Failed pipeline] avm.res.network.load-balancer #1314
Comments
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
Note This message was posted as per ITA01BCP. |
Azure Load-Balancer can only support zones for subnet frontends and not for public IP frontend load balancers. A issue is opened with the PSRule team to modify their rule to test for this condition. Azure/PSRule.Rules.Azure#2814 |
@rahalan @matebarabas FYI although the latest pipeline run for this module succeeded, this issue has not been closed |
## Description <!-- >Thank you for your contribution ! > Please include a summary of the change and which issue is fixed. > Please also include the context. > List any dependencies that are required for this change. --> This PR contains a new AVM resource for the Microsoft.Network/p2svpnGateways resource provider, which builds a P2S VPN Gateway within a VWAN Virtual Hub. This resource requires a Virtual WAN and Virtual Hub, as well as a VPN Server Configuration to deploy successfully. Closes [#1314](Azure/Azure-Verified-Modules#1314) ## Pipeline Reference <!-- Insert your Pipeline Status Badge below --> [![avm.res.network.p2s-vpn-gateway](https://github.com/ericscheffler/bicep-registry-modules/actions/workflows/avm.res.network.p2s-vpn-gateway.yml/badge.svg?branch=Issue1314-p2s-vpn-gateway)](https://github.com/ericscheffler/bicep-registry-modules/actions/workflows/avm.res.network.p2s-vpn-gateway.yml) ## Type of Change <!-- Use the checkboxes [x] on the options that are relevant. --> - [ ] Update to CI Environment or utilities (Non-module affecting changes) - [x] Azure Verified Module updates: - [ ] Bugfix containing backwards-compatible bug fixes, and I have NOT bumped the MAJOR or MINOR version in `version.json`: - [ ] Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description. - [ ] The bug was found by the module author, and no one has opened an issue to report it yet. - [ ] Feature update backwards compatible feature updates, and I have bumped the MINOR version in `version.json`. - [ ] Breaking changes and I have bumped the MAJOR version in `version.json`. - [ ] Update to documentation ## Checklist - [x] I'm sure there are no other open Pull Requests for the same update/change - [x] I have run `Set-AVMModule` locally to generate the supporting module files. - [x] My corresponding pipelines / checks run clean and green without any errors or warnings <!-- Please keep up to date with the contribution guide at https://aka.ms/avm/contribute/bicep --> --------- Co-authored-by: erschef_microsoft <[email protected]>
Failed run: https://github.com/Azure/bicep-registry-modules/actions/runs/8307588658
The text was updated successfully, but these errors were encountered: