[Modules] Fix API version issues

[MariusStorhaug]

Description

All pipelines be breaking on my end, so thought I would just bump a version and regen all files.

• API version bump of modules:
  • applicationGateways (2022-07-01) -> (2023-05-01)
  • applicationSecurityGroups (2022-07-01) -> (2023-05-01)
  • azureFirewalls (2022-07-01) -> (2023-05-01)
  • connections (2022-07-01) -> (2023-05-01)
  • ddosProtectionPlans (2022-07-01) -> (2023-05-01)
  • expressRouteCircuits (2022-07-01) -> (2023-05-01)
  • firewallPolicies (2022-07-01) -> (2023-05-01)
  • ipGroups (2022-07-01) -> (2023-05-01)
  • loadBalancers (2022-07-01) -> (2023-05-01)
  • localNetworkGateways (2022-07-01) -> (2023-05-01)
  • natGateways (2022-07-01) -> (2023-05-01)
  • networkInterfaces (2022-07-01) -> (2023-05-01)
  • networkSecurityGroups (2022-07-01) -> (2023-05-01)
  • networkWatchers (2022-07-01) -> (2023-05-01)
  • networkWatchers/connectionMonitors (2022-07-01) -> (2023-05-01)
  • networkWatchers/connectionMonitors (2022-07-01) -> (2023-05-01)
  • networkWatchers/flowLogs (2022-07-01) -> (2023-05-01)
  • networkWatchers/flowLogs (2022-07-01) -> (2023-05-01)
  • privateEndpoints (2022-07-01) -> (2023-05-01)
  • privateEndpoints/privateDnsZoneGroups (2022-07-01) -> (2023-04-01)
  • publicIPAddresses (2022-07-01) -> (2023-05-01)
  • publicIPPrefixes (2022-07-01) -> (2023-05-01)
  • routeTables (2022-07-01) -> (2023-05-01)
  • serviceEndpointPolicies (2022-07-01) -> (2023-05-01)
  • virtualNetworkGateways (2022-07-01) -> (2023-05-01)
  • virtualNetworks (2022-07-01) -> (2023-05-01)
  • virtualWans (2022-07-01) -> (2023-05-01)
  • vpnGateways (2022-07-01) -> (2023-05-01)
  • vpnSites (2022-07-01) -> (2023-05-01)
• Regen readme and ARM templates for all modules.

Pipeline references

Pipeline

Type of Change

Please delete options that are not relevant.

• Patch (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Update to documentation

Checklist

• I'm sure there are no other open Pull Requests for the same update/change
• My corresponding pipelines / checks run clean and green without any errors or warnings
• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (readme)
• I did format my code

[MariusStorhaug]

I have a very limited environment on my own side, so let me know which pipelines you might want me to run. If possible, might be worth pulling it in to a branch in Azure/ResourceModules and run a test from there if possible.

[eriqua]

Hey @MariusStorhaug, as we're currently working on a dev branch to rename all module folders to a singular form and comply with the public Bicep registry naming, I'm putting on hold this PR until #3571 and #3573 are merged

[MariusStorhaug]

@AlexanderSehr @eriqua : I see more breakages in pipeline due to APIs growing old. Want me to include them in this PR or a separate one? A significant one is the networking RP.

[MariusStorhaug]

Merge conflict resolved by regening the host-pools main.json file.

[AlexanderSehr]

@AlexanderSehr @eriqua : I see more breakages in pipeline due to APIs growing old. Want me to include them in this PR or a separate one? A significant one is the networking RP.

Though it pains me to say, I'd suggest to wait to limit conflicts with the upcoming breaking changes.

[MariusStorhaug]

@AlexanderSehr @eriqua : I see more breakages in pipeline due to APIs growing old. Want me to include them in this PR or a separate one? A significant one is the networking RP.

Though it pains me to say, I'd suggest to wait to limit conflicts with the upcoming breaking changes.

Any ETA for that change? :)

[AlexanderSehr]

@AlexanderSehr @eriqua : I see more breakages in pipeline due to APIs growing old. Want me to include them in this PR or a separate one? A significant one is the networking RP.

Though it pains me to say, I'd suggest to wait to limit conflicts with the upcoming breaking changes.

Any ETA for that change? :)

Weeks ago 😬 but we're though most of it. So I'd expect within the next week or two

[eriqua]

@AlexanderSehr @eriqua : I see more breakages in pipeline due to APIs growing old. Want me to include them in this PR or a separate one? A significant one is the networking RP.

Though it pains me to say, I'd suggest to wait to limit conflicts with the upcoming breaking changes.

Any ETA for that change? :)

@AlexanderSehr @eriqua : I see more breakages in pipeline due to APIs growing old. Want me to include them in this PR or a separate one? A significant one is the networking RP.

Though it pains me to say, I'd suggest to wait to limit conflicts with the upcoming breaking changes.

Any ETA for that change? :)

Weeks ago 😬 but we're though most of it. So I'd expect within the next week or two

As soon as PR #3573 gets merged 👯

[AlexanderSehr]

@AlexanderSehr @eriqua : I see more breakages in pipeline due to APIs growing old. Want me to include them in this PR or a separate one? A significant one is the networking RP.

Though it pains me to say, I'd suggest to wait to limit conflicts with the upcoming breaking changes.

Any ETA for that change? :)

@AlexanderSehr @eriqua : I see more breakages in pipeline due to APIs growing old. Want me to include them in this PR or a separate one? A significant one is the networking RP.

Though it pains me to say, I'd suggest to wait to limit conflicts with the upcoming breaking changes.

Any ETA for that change? :)

Weeks ago 😬 but we're though most of it. So I'd expect within the next week or two

As soon as PR #3573 gets merged 👯

PR is merged. Now we have to fix a bunch of Api versions 😄

[MariusStorhaug]

Too many conflicts to care. Reboot PR: #3665