Skip to content
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

Closed
github-actions bot opened this issue Mar 17, 2024 · 14 comments
Closed

[Failed pipeline] avm.res.network.load-balancer #1314

github-actions bot opened this issue Mar 17, 2024 · 14 comments
Assignees
Labels
Type: AVM 🅰️ ✌️ Ⓜ️ This is an AVM related issue Type: Bug 🐛 Something isn't working

Comments

@github-actions
Copy link
Contributor

Failed run: https://github.com/Azure/bicep-registry-modules/actions/runs/8307588658

@github-actions github-actions bot added Type: AVM 🅰️ ✌️ Ⓜ️ This is an AVM related issue Type: Bug 🐛 Something isn't working labels Mar 17, 2024
@github-project-automation github-project-automation bot moved this to Todo in Bicep Mar 17, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs: Triage 🔍 Maintainers need to triage still label Mar 17, 2024
Copy link
Contributor Author

Copy link
Contributor Author

Copy link
Contributor Author

Copy link
Contributor Author

Copy link
Contributor Author

Copy link
Contributor Author

Copy link
Contributor Author

Copy link
Contributor Author

Copy link
Contributor Author

github-actions bot commented Apr 1, 2024

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 🔍" label must be removed as part of the triage process (when the issue is first responded to)!

Note

This message was posted as per ITA01BCP.

@microsoft-github-policy-service microsoft-github-policy-service bot added the Status: Response Overdue 🚩 When an issue/PR has not been responded to for X amount of days label Apr 9, 2024
@arnoldna arnoldna removed Needs: Triage 🔍 Maintainers need to triage still Status: Response Overdue 🚩 When an issue/PR has not been responded to for X amount of days labels Apr 9, 2024
@arnoldna
Copy link
Contributor

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

Copy link
Contributor Author

@eriqua
Copy link
Contributor

eriqua commented Apr 15, 2024

@rahalan @matebarabas FYI although the latest pipeline run for this module succeeded, this issue has not been closed

Copy link

@github-project-automation github-project-automation bot moved this from Todo to Done in Bicep Apr 22, 2024
@github-project-automation github-project-automation bot moved this from Needs: Triage to Done in AVM - Module Issues Apr 22, 2024
AlexanderSehr pushed a commit that referenced this issue Dec 10, 2024
## 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]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: AVM 🅰️ ✌️ Ⓜ️ This is an AVM related issue Type: Bug 🐛 Something isn't working
Projects
Archived in project
Development

No branches or pull requests

3 participants