Closed chris5287 closed 2 weeks ago
I will investigate this bug
@chris5287 I'm having trouble reproducing the issue. The module deployment using module pipeline worked for me, also changing the "ConnectionBandwidth" property was successful. Can you please share more details, which could help me to reproduce the issue? For example: In which region are you deploying, are you using the latest version of the modules?
I was using 0.6.0 deploying into the uksouth and canadacentral regions
Hey @fabmas, I just migrated this issue from CARML. Please take a look an triage. Maybe it's not relevant anymore :)
Hey @fabmas, please take a moment to triage this issue if you can 💪
Hey, sorry for the delay. I'm currently restructuring the entire module introducing new UDTs. I'll take care of this issue in the next release of the module.
Hey @fabmas,
thanks. Just note that the CI's automation (bot) will continue to comment and ping you until the labels Needs: Triage
and Status: Response Overdue
are removed 😉
This issue is no more relevant.
Describe the bug
It appears the
ConnectionBandwidth
property has been deprecated, but the ARM docs haven't been updated here: https://docs.microsoft.com/en-us/azure/templates/microsoft.network/vpngateways/vpnconnections?tabs=bicep#vpnconnectionpropertiesThis means deployments fail and there is no way to use the module as it has a default value in the bicep file :(
To reproduce
https://github.com/Azure/ResourceModules/blob/80c29bd5fef1d522354b801b6bb59106e74ad67c/modules/Microsoft.Network/vpnGateways/connections/deploy.bicep#L38
https://github.com/Azure/ResourceModules/blob/80c29bd5fef1d522354b801b6bb59106e74ad67c/modules/Microsoft.Network/vpnGateways/connections/deploy.bicep#L76
Code snippet
Relevant log output