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.

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

Microsoft.Network/connections #2831

Open
StephenWeatherford opened this issue Mar 10, 2023 · 0 comments
Open

Microsoft.Network/connections #2831

StephenWeatherford opened this issue Mar 10, 2023 · 0 comments

Comments

@StephenWeatherford
Copy link

Given this JSON:

{
	"$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
	"contentVersion": "1.0.0.0",
	"resources": [
		{
			"name": "vpnVnetConnection1",
			"type": "Microsoft.Network/connections",
			"apiVersion": "2020-11-01",
			"location": "[resourceGroup().location]",
			"dependsOn": [
				"[resourceId('Microsoft.Network/virtualNetworkGateways', 'vnetGateway1')]",
				"[resourceId('Microsoft.Network/localNetworkGateways', 'localGateway1')]"
			],
			"properties": {
				"virtualNetworkGateway1": {
					"id": "[resourceId('Microsoft.Network/virtualNetworkGateways', 'vnetGateway1')]"
				},
				"localNetworkGateway2": {
					"id": "[resourceId('Microsoft.Network/localNetworkGateways', 'localGateway1')]"
				},
				"connectionType": "IPsec",
				"routingWeight": 0,
				"sharedKey": "sharedkey"
			}
		}
	]
}

... the JSON validation fails with:

image

A schema should never require a "properties" object to be present when there are no required properties in it.

EXPECTED: No schema validation errors

@ghost ghost added the Needs: Triage 🔎 label Mar 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant