There is a command group 'az_databricks_workspace_vnet peering'. This group of commands could 'commands to manage databricks workspace vnet peering'. The group of commands has global parameter '--debug' which means 'Increase logging verbosity to show all debug logs.'. The group of commands has global parameter '--help -h' which means 'Show this help message and exit.'. The group of commands has global parameter '--only-show-errors' which means 'Only show errors, suppressing warnings.'. The group of commands has global parameter '--output -o' which means 'Output format.'. The group of commands has global parameter '--query' which means 'JMESPath query string. See <a href="http://jmespath.org/">http://jmespath.org/</a> for more information and examples.'. The group of commands has global parameter '--subscription' which means 'Name or ID of subscription. You can configure the default subscription using `az account set -s NAME_OR_ID`.'. The group of commands has global parameter '--verbose' which means 'Increase logging verbosity. Use --debug for full debug logs.'. This group contains a child command 'az_databricks_workspace_vnet peering_create'.The syntax is: az databricks workspace vnet-peering create --name
                                            --resource-group
                                            --workspace-name
                                            [--allow-forwarded-traffic {0, 1, f, false, n, no, t, true, y, yes}]
                                            [--allow-gateway-transit {0, 1, f, false, n, no, t, true, y, yes}]
                                            [--allow-virtual-network-access {0, 1, f, false, n, no, t, true, y, yes}]
                                            [--no-wait {0, 1, f, false, n, no, t, true, y, yes}]
                                            [--remote-vnet]
                                            [--use-remote-gateways {0, 1, f, false, n, no, t, true, y, yes}]. The 1th example of the child command would be to use it to 'create a vnet peering for a workspace', the syntax is: az databricks workspace vnet-peering create --resource-group MyResourceGroup --workspace-name MyWorkspace -n MyPeering --remote-vnet /subscriptions/000000-0000-0000/resourceGroups/MyRG/providers/Microsoft.Network/virtualNetworks/MyVNet. The parameter '--name -n' is required. It is used to the name of the vnet peering.. The parameter '--resource-group -g' is required. It is used to name of resource group. you can configure the default group using `az configure --defaults group=<name>`.. The parameter '--workspace-name' is required. It is used to the name of the workspace.. The parameter '--allow-forwarded-traffic' is optional. whether the forwarded traffic from the vms in the local virtual network will be allowed/disallowed in remote virtual network.. The parameter '--allow-gateway-transit' is optional. if gateway links can be used in remote virtual networking to link to this virtual network.. The parameter '--allow-virtual-network-access' is optional. whether the vms in the local virtual network space would be able to access the vms in remote virtual network space.. The parameter '--no-wait' is optional. do not wait for the long-running operation to finish.. The parameter '--remote-vnet' is optional. the remote virtual network name or resource id.. The parameter '--use-remote-gateways' is optional. 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.. 