-
Notifications
You must be signed in to change notification settings - Fork 362
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
feat: module avm/res/network/virtual-network-gateway
#3639
base: main
Are you sure you want to change the base?
Changes from 16 commits
d83c5a0
f3e9a69
b001fec
84937cd
20af928
4ad24d2
43c8037
45a0428
baa4bfa
b692a78
e42fe7d
04b0263
26fcbaa
9dfc123
bb43a8c
2ace889
0d1a848
ed8d4cd
fe3544f
f62cd68
e2a3e00
bda1728
540a6ee
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Just a heads up as I noticed your test pipeline failed. |
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -494,6 +494,31 @@ output activeActive bool = virtualNetworkGateway.properties.activeActive | |
@description('The location the resource was deployed into.') | ||
output location string = virtualNetworkGateway.location | ||
|
||
@description('The ASN (Autonomous System Number) of the virtual network gateway.') | ||
output asn int? = virtualNetworkGateway.properties.bgpSettings.asn | ||
|
||
@description('The IPconfigurations object of the Virtual Network Gateway.') | ||
output ipConfigurations array? = virtualNetworkGateway.properties.ipConfigurations | ||
|
||
@description('The public IP address of the virtual network gateway.') | ||
output publicIpAddress string = !empty(existingFirstPipResourceId) ? reference(existingFirstPipResourceId,'2023-04-01').ipAddress: publicIPAddress[0].outputs.ipAddress | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. can't this be retrieved as a virtualNetworkGateway property? No matter if existing or not before the deployment? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Also in this case we could provide primary and secondary pip as part of a publicIp output object |
||
|
||
@description('The default Azure BGP peer IP address.') | ||
output defaultBgpIpAddresses string? = isBgp ? join(virtualNetworkGateway.properties.bgpSettings.bgpPeeringAddresses[0].defaultBgpIpAddresses, ','): null //'Not applicable (No Bgp)' | ||
|
||
@description('The custom Azure APIPA BGP IP address.') | ||
output customBgpIpAddresses string? = isBgp ? join(virtualNetworkGateway.properties.bgpSettings.bgpPeeringAddresses[0].customBgpIpAddresses, ','): null //'Not applicable (No Bgp)' | ||
|
||
@description('The second public IP address of the virtual network gateway (Active-Active mode).') | ||
output secondPublicIpAddress string? = isActiveActive ? !empty(existingSecondPipResourceIdVar) ? reference(existingSecondPipResourceIdVar,'2023-04-01').ipAddress: publicIPAddress[1].outputs.ipAddress: null // 'Not applicable (Active-Passive mode)' | ||
|
||
@description('The second default Azure BGP peer IP address (Active-Active mode).') | ||
output secondBgpIpAddress string? = isActiveActive && isBgp ? join(virtualNetworkGateway.properties.bgpSettings.bgpPeeringAddresses[1].defaultBgpIpAddresses, ','): null //'Not applicable (Active-Passive mode)' | ||
|
||
@description('The second custom Azure APIPA BGP IP address (Active-Active mode).') | ||
output secondCustomBgpIpAddress string? = isActiveActive && isBgp ? join(virtualNetworkGateway.properties.bgpSettings.bgpPeeringAddresses[1].customBgpIpAddresses, ','): null //'Not applicable (Active-Passive mode)' | ||
|
||
|
||
// =============== // | ||
// Definitions // | ||
// =============== // | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please note, the
main.json
templates must be re-build with the latest Bicep version0.31.34
as this version (running on the agents) renders a differentmain.json
file then previous versions.The steps to execute would be
0.31.34
(e.g. viachoco upgrade bicep
if choco is used)Set-AVMModule
script on your module. E.g. viaSet-AVMModule -ModuleFolderPath '.\avm\res\automation\automation-account\' -SkipFileAndFolderSetup -SkipReadMe -Recurse
If the static tests continue to fail for you, please note that there is currently presumably another new bug which affects some of our modules (ref).