VirtualNetworkPeering Class
Peerings in a VirtualNetwork resource.
Variables are only populated by the server, and will be ignored when sending a request.
All required parameters must be populated in order to send to Azure.
- Inheritance
-
azure.mgmt.databricks._serialization.ModelVirtualNetworkPeering
Constructor
VirtualNetworkPeering(*, remote_virtual_network: _models.VirtualNetworkPeeringPropertiesFormatRemoteVirtualNetwork, allow_virtual_network_access: bool | None = None, allow_forwarded_traffic: bool | None = None, allow_gateway_transit: bool | None = None, use_remote_gateways: bool | None = None, databricks_virtual_network: _models.VirtualNetworkPeeringPropertiesFormatDatabricksVirtualNetwork | None = None, databricks_address_space: _models.AddressSpace | None = None, remote_address_space: _models.AddressSpace | None = None, **kwargs: Any)
Keyword-Only Parameters
Name | Description |
---|---|
allow_virtual_network_access
|
Whether the VMs in the local virtual network space would be able to access the VMs in remote virtual network space. |
allow_forwarded_traffic
|
Whether the forwarded traffic from the VMs in the local virtual network will be allowed/disallowed in remote virtual network. |
allow_gateway_transit
|
If gateway links can be used in remote virtual networking to link to this virtual network. |
use_remote_gateways
|
If remote gateways can be used on this virtual network. If the flag is set to true, and allowGatewayTransit on remote peering is also true, virtual network will use gateways of remote virtual network for transit. Only one peering can have this flag set to true. This flag cannot be set if virtual network already has a gateway. |
databricks_virtual_network
|
The remote virtual network should be in the same region. See here to learn more (https://docs.microsoft.com/en-us/azure/databricks/administration-guide/cloud-configurations/azure/vnet-peering). |
databricks_address_space
|
The reference to the databricks virtual network address space. |
remote_virtual_network
|
The remote virtual network should be in the same region. See here to learn more (https://docs.microsoft.com/en-us/azure/databricks/administration-guide/cloud-configurations/azure/vnet-peering). Required. |
remote_address_space
|
The reference to the remote virtual network address space. |
Variables
Name | Description |
---|---|
name
|
Name of the virtual network peering resource. |
id
|
Resource ID. |
type
|
type of the virtual network peering resource. |
allow_virtual_network_access
|
Whether the VMs in the local virtual network space would be able to access the VMs in remote virtual network space. |
allow_forwarded_traffic
|
Whether the forwarded traffic from the VMs in the local virtual network will be allowed/disallowed in remote virtual network. |
allow_gateway_transit
|
If gateway links can be used in remote virtual networking to link to this virtual network. |
use_remote_gateways
|
If remote gateways can be used on this virtual network. If the flag is set to true, and allowGatewayTransit on remote peering is also true, virtual network will use gateways of remote virtual network for transit. Only one peering can have this flag set to true. This flag cannot be set if virtual network already has a gateway. |
databricks_virtual_network
|
The remote virtual network should be in the same region. See here to learn more (https://docs.microsoft.com/en-us/azure/databricks/administration-guide/cloud-configurations/azure/vnet-peering). |
databricks_address_space
|
The reference to the databricks virtual network address space. |
remote_virtual_network
|
The remote virtual network should be in the same region. See here to learn more (https://docs.microsoft.com/en-us/azure/databricks/administration-guide/cloud-configurations/azure/vnet-peering). Required. |
remote_address_space
|
The reference to the remote virtual network address space. |
peering_state
|
str or
PeeringState
The status of the virtual network peering. Known values are: "Initiated", "Connected", and "Disconnected". |
provisioning_state
|
The provisioning state of the virtual network peering resource. Known values are: "Succeeded", "Updating", "Deleting", and "Failed". |
Azure SDK for Python
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for