-
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?
Conversation
@@ -494,6 +494,28 @@ 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? = isBgp ? virtualNetworkGateway.properties.bgpSettings.asn : null //'Not applicable (No Bgp)' |
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.
This should be enough
output asn int? = isBgp ? virtualNetworkGateway.properties.bgpSettings.asn : null //'Not applicable (No Bgp)' | |
output asn int? = virtualNetworkGateway.properties.bgpSettings.asn |
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.
In general instead of providing multiple top level properties I wonder if cleaner to provide a bgp object as output
output asn int? = isBgp ? virtualNetworkGateway.properties.bgpSettings.asn : null //'Not applicable (No Bgp)' | ||
|
||
@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 comment
The 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 comment
The 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
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.
Just a heads up as I noticed your test pipeline failed.
A new test is checking weather Required parameters have a default value. In that case it fails, since if a parameter has a default value is Optional by definition.
This is the case for the skuName parameter.
Changing the description to Optional should fix the issue
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 version 0.31.34
as this version (running on the agents) renders a different main.json
file then previous versions.
The steps to execute would be
- Upgrade your Bicep CLI version to
0.31.34
(e.g. viachoco upgrade bicep
if choco is used) - Re-run the
Set-AVMModule
script on your module. E.g. viaSet-AVMModule -ModuleFolderPath '.\avm\res\automation\automation-account\' -SkipFileAndFolderSetup -SkipReadMe -Recurse
- Push the changes
- Re-run the tests to ensure everything works.
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).
Hey @fabmas , Firstly, thanks for your work on this PR! We have made some changes to the AVM CI, detailed below, which means we need you to update your fork to pull in these latest changes and re-run your tests to show they still are passing prior to approving and merging this PR, as we don't and it fails once merged the publishing of your module will fail and will be blocked going forward until the test pass again via additional PRs. Changes to CI That Have Been Made That You Need To Take Action On
Any questions reach out to the AVM Core Team by tagging us in your PR here or internally via Teams Thanks Jack (AVM Core Team) |
Description
Added input requested in #3493
Closes #3493
Pipeline Reference
Type of Change
version.json
:version.json
.version.json
.Checklist
Set-AVMModule
locally to generate the supporting module files.