question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Add option for remote VNET peer name

See original GitHub issue

Library or service name. What library or service is this request related to? Microsoft.Azure.Management.Network.Fluent

Is your feature request related to a problem? Please describe. No way to define name of the peering from remote virtual network using Azure Management API

Actual Result

While running below code it is establishing the peer with random name at remote vnet end.

hubVNet.Peerings
                .Define("hub-to-spoke1-peering")
                .WithRemoteNetwork(spoke1VNet.Id)
                .Create();

image

Expected Result While defining .Define("hub-to-spoke1-peering") is showing this value as source VNet peer name. User should be able to define the peer name for remote VNet as well.

Or, Management API should also work as az cli i.e it should not auto establish the peering between two VNet, while using az network vnet peering create -g "sandbox" -n "spoke1-to-hub-peering" --vnet-name "spoke1-vnet" --remote-vnet "/subscriptions/xxx/resourceGroups/sandbox/providers/Microsoft.Network/virtualNetworks/hub-vnet" --allow-vnet-access it only initiate the peer request from source vnet and to establish the connection user needs to create another peering from destination.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Reactions:1
  • Comments:7 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
xseeseeseecommented, Jan 13, 2021

@anktsrkr It looks this is the line we define a random remote peer name internally. If you want to have your own value for the name, you may want to consider taking the whole block code for resource creation now.

cc: @nickzhums We may consider to improve this in new .NET SDK.

1reaction
jsquirecommented, Sep 5, 2020

Thank you for your feedback. Tagging and routing to the team member best able to assist.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Create, change, or delete an Azure virtual network peering
Select Peerings under Settings and then select + Add. Screenshot of peerings page for VNetA. Enter or select values for the following settings, ......
Read more >
Connect virtual networks with VNet peering - Azure portal
Peering link name, Enter myVirtualNetwork2-myVirtualNetwork1 for the name of the peering from the remote virtual network to myVirtualNetwork1.
Read more >
Azure – How to Configure vNet Peering
Click Peerings and then click Add. On the Add Peering page enter a name for the peering, and select the Virtual Network to...
Read more >
Tip 182 - Use VNET peering to connect existing VNETs
In the Azure portal, I go to the hub-vnet virtual network, select Peerings, and click the Add button. I give the peering the...
Read more >
Step by Step guide on setting up Azure vNet Peering
Navigate to your second vNet and click Peerings. ... In the new blade enter a Name for this peering, select the Subscription that...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found