Virtual network peering enables you to seamlessly connect two or more Virtual Networks in Azure. The virtual networks appear as one for connectivity purposes. The traffic between virtual machines in peered virtual networks uses the Microsoft backbone infrastructure. Like traffic between virtual machines in the same network, traffic is routed through Microsoft's private network only.
For detailed information, check out our Operator Guide for this bundle.
Our bundles aren't intended to be used locally, outside of testing. Instead, our bundles are designed to be configured, connected, deployed and monitored in the Massdriver platform.
Bundles are the basic building blocks of infrastructure, applications, and architectures in Massdriver. Read more here.
Form input parameters for configuring a bundle for deployment.
View
-
accepter_vnet_id(string): IMPORTANT: Only set this value if you haven't connected a remote "accepter" VNet to the bundle. If an accepter VNet is connected, this field is ignored and the value will be extracted from the connection. Use this field if the remote VNet isn't managed by Massdriver or exists in a different subscription than the requester VNet. The CIDRs of the requester and accepter VNets must not overlap. This will require you to resync the peering connection of the accepter VNet manually (instructions in bundle Guide)!Examples:
"/subscriptions/12345678-1234-1234-abcd-1234567890ab/resourceGroups/resource-group-name/providers/Microsoft.Network/virtualNetworks/network-name"
Connections from other bundles that this bundle depends on.
View
accepter(object): . Cannot contain additional properties.-
data(object)infrastructure(object)-
cidr(string)Examples:
"10.100.0.0/16""192.24.12.0/22" -
default_subnet_id(string): Azure Resource ID.Examples:
"/subscriptions/12345678-1234-1234-abcd-1234567890ab/resourceGroups/resource-group-name/providers/Microsoft.Network/virtualNetworks/network-name" -
id(string): Azure Resource ID.Examples:
"/subscriptions/12345678-1234-1234-abcd-1234567890ab/resourceGroups/resource-group-name/providers/Microsoft.Network/virtualNetworks/network-name"
-
-
specs(object)azure(object): .region(string): Select the Azure region you'd like to provision your resources in.
-
azure_service_principal(object): . Cannot contain additional properties.-
data(object)-
client_id(string): A valid UUID field.Examples:
"123xyz99-ab34-56cd-e7f8-456abc1q2w3e" -
client_secret(string) -
subscription_id(string): A valid UUID field.Examples:
"123xyz99-ab34-56cd-e7f8-456abc1q2w3e" -
tenant_id(string): A valid UUID field.Examples:
"123xyz99-ab34-56cd-e7f8-456abc1q2w3e"
-
-
specs(object)
-
requester(object): . Cannot contain additional properties.-
data(object)infrastructure(object)-
cidr(string)Examples:
"10.100.0.0/16""192.24.12.0/22" -
default_subnet_id(string): Azure Resource ID.Examples:
"/subscriptions/12345678-1234-1234-abcd-1234567890ab/resourceGroups/resource-group-name/providers/Microsoft.Network/virtualNetworks/network-name" -
id(string): Azure Resource ID.Examples:
"/subscriptions/12345678-1234-1234-abcd-1234567890ab/resourceGroups/resource-group-name/providers/Microsoft.Network/virtualNetworks/network-name"
-
-
specs(object)azure(object): .region(string): Select the Azure region you'd like to provision your resources in.
-
Resources created by this bundle that can be connected to other bundles.
Did we miss something? Please submit an issue to report any bugs or request additional features.
Note: Massdriver bundles are intended to be tightly use-case scoped, intention-based, reusable pieces of IaC for use in the Massdriver platform. For this reason, major feature additions that broaden the scope of an existing bundle are likely to be rejected by the community.
Still want to get involved? First check out our contribution guidelines.
If your use-case isn't covered by this bundle, you can still get involved! Massdriver is designed to be an extensible platform. Fork this bundle, or create your own bundle from scratch!
Questions? Concerns? Adulations? We'd love to hear from you!
Please connect with us!
