-
Notifications
You must be signed in to change notification settings - Fork 514
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
hubNetworking: Make examples working with WhatIf mode #302
Conversation
Marked this one as draft for now because I didn't had time to re-run this in empty environment and collect evidences. And some of those changes might need discussion if I'm solving them correct way. Also it might be that if #252 gets merged first there will be conflicts. |
76891a0
to
1e1fcda
Compare
9499b21
to
83bab96
Compare
83bab96
to
529f257
Compare
@jtracey93 I can see that #306 was merged so I updated this one. Can you take first look if this something which can be included here? (assuming that it passes tests and readme is updated). |
782252c
to
3e9041b
Compare
ping @jtracey93 |
Is this just laying around? There are multiple issues with hub-spoke peering reported here here that would be fixed by this PR @jtracey93 |
@Strandfelt as far I understand the challenge is that it is unclear inside of Microsoft that who/where those challenges should be fixed? Options are Azure API's, API clients like Bicep and actual client applications like this repository. And because this PR was not approved, I don't expect to see this solved anytime soon. If we can find couple of persons who are interested enough about topic, it would be possible quite easily to build custom WhatIf tester which can handle those bugs in API. I once started to build that kind of in https://github.com/olljanat/alz-bicep-ci/blob/ps-whatif/PSAzureAPI/PSAzureAPI.psm1 |
Closing as stale |
Overview/Summary
Solving multiple issues with WhatIf mode in Hub Networking.
This PR fixes/adds/changes/removes
Related to hub networking part of #249
However WhatIf test cannot be yet enabled to CI because
Microsoft.Network/virtualNetworkGateways
does report that it would removeproperties.remoteVirtualNetworkPeerings
andMicrosoft.Network/virtualNetworks
reports that it would removeproperties.virtualNetworkPeerings
both of those are just noise Azure/arm-template-whatif#233Breaking Changes
N/A
Testing Evidence
Not yet...
As part of this Pull Request I have
.bicep
file/s I am adding/editing are using the latest API version possiblemain
branch