Skip to content
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

Closed
wants to merge 3 commits into from

Conversation

olljanat
Copy link
Contributor

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 remove properties.remoteVirtualNetworkPeerings and Microsoft.Network/virtualNetworks reports that it would remove properties.virtualNetworkPeerings both of those are just noise Azure/arm-template-whatif#233

Breaking Changes

N/A

Testing Evidence

Not yet...

As part of this Pull Request I have

@ghost ghost added the Needs: Triage 🔍 Needs triaging by the team label Aug 11, 2022
@olljanat olljanat marked this pull request as draft August 11, 2022 13:04
@olljanat
Copy link
Contributor Author

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.

@olljanat
Copy link
Contributor Author

olljanat commented Sep 6, 2022

Looks that version of #252 which finally got merged didn't have conflicts with this one so I rebased it with main branch. However now there looks to be new PR #306 which touches same area.

@olljanat olljanat force-pushed the hubnetwork-whatif-fixes branch 2 times, most recently from 9499b21 to 83bab96 Compare October 19, 2022 11:36
@olljanat olljanat marked this pull request as ready for review October 19, 2022 12:04
@olljanat olljanat marked this pull request as draft October 19, 2022 12:04
@olljanat olljanat marked this pull request as ready for review October 19, 2022 14:44
@olljanat
Copy link
Contributor Author

@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).

@olljanat
Copy link
Contributor Author

ping @jtracey93

@Strandfelt
Copy link

Is this just laying around? There are multiple issues with hub-spoke peering reported here here that would be fixed by this PR @jtracey93

@olljanat
Copy link
Contributor Author

@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

@jtracey93
Copy link
Contributor

Closing as stale

@jtracey93 jtracey93 closed this Oct 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needs: Triage 🔍 Needs triaging by the team
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants