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.

Sign up for GitHub

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

Jump to bottom

Potential mistake on grabbing the network resource ID in the hub peering Bicep #450

Closed
pedalingcircles opened this issue Oct 11, 2021 · 1 comment · Fixed by #451
Closed

Potential mistake on grabbing the network resource ID in the hub peering Bicep #450

pedalingcircles opened this issue Oct 11, 2021 · 1 comment · Fixed by #451
Assignees
@glennmusa
Labels
bug Something isn't working

Comments

@pedalingcircles
Copy link

missionlz/src/bicep/mlz.bicep

Line 215 in a3a6022

operationsVirtualNetworkResourceId: sharedServices.outputs.virtualNetworkResourceId

It looks like a maybe a small copy paste mistake on grabbing the virtual network resource ids. The identity looks good but the ops and shared services look swapped.
@glennmusa glennmusa self-assigned this Oct 11, 2021
@glennmusa glennmusa added the bug Something isn't working label Oct 11, 2021
@glennmusa
Copy link
Contributor

thanks for reporting this @pedalingcircles 👍

@glennmusa glennmusa mentioned this issue Oct 11, 2021
Merged
4 tasks
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@glennmusa glennmusa

Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix transposed hub network peerings Azure/missionlz
2 participants
@glennmusa @pedalingcircles