Skip to content

Commit 6e44cc3

Browse files
authored
Merge pull request #111968 from mumian/0420-schema
update schema version
2 parents cbae96e + ff2ce92 commit 6e44cc3

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

articles/azure-resource-manager/templates/parameter-files.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Create parameter file
33
description: Create parameter file for passing in values during deployment of an Azure Resource Manager template
44
ms.topic: conceptual
5-
ms.date: 08/21/2019
5+
ms.date: 04/20/2020
66
---
77
# Create Resource Manager parameter file
88

@@ -14,7 +14,7 @@ The parameter file has the following format:
1414

1515
```json
1616
{
17-
"$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#",
17+
"$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentParameters.json#",
1818
"contentVersion": "1.0.0.0",
1919
"parameters": {
2020
"<first-parameter-name>": {
@@ -33,7 +33,7 @@ The following parameter file includes a plain text value and a value that is sto
3333

3434
```json
3535
{
36-
"$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#",
36+
"$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentParameters.json#",
3737
"contentVersion": "1.0.0.0",
3838
"parameters": {
3939
"<first-parameter-name>": {
@@ -80,7 +80,7 @@ The first detail to notice is the name of each parameter. The values in your par
8080

8181
```json
8282
{
83-
"$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#",
83+
"$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentParameters.json#",
8484
"contentVersion": "1.0.0.0",
8585
"parameters": {
8686
"storagePrefix": {
@@ -95,7 +95,7 @@ Notice the type of the parameter. The values in your parameter file must have th
9595

9696
```json
9797
{
98-
"$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#",
98+
"$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentParameters.json#",
9999
"contentVersion": "1.0.0.0",
100100
"parameters": {
101101
"storagePrefix": {
@@ -112,7 +112,7 @@ Next, look for a default value. If a parameter has a default value, you can prov
112112

113113
```json
114114
{
115-
"$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#",
115+
"$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentParameters.json#",
116116
"contentVersion": "1.0.0.0",
117117
"parameters": {
118118
"storagePrefix": {
@@ -129,7 +129,7 @@ Finally, look at the allowed values and any restrictions like max length. They t
129129

130130
```json
131131
{
132-
"$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#",
132+
"$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentParameters.json#",
133133
"contentVersion": "1.0.0.0",
134134
"parameters": {
135135
"storagePrefix": {
@@ -148,7 +148,7 @@ The following example shows the formats of different parameter types.
148148

149149
```json
150150
{
151-
"$schema": "https://schema.management.azure.com/schemas/2015-01-01/deploymentParameters.json#",
151+
"$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentParameters.json#",
152152
"contentVersion": "1.0.0.0",
153153
"parameters": {
154154
"exampleString": {

0 commit comments

Comments
 (0)