2
2
title : Create parameter file
3
3
description : Create parameter file for passing in values during deployment of an Azure Resource Manager template
4
4
ms.topic : conceptual
5
- ms.date : 08/21/2019
5
+ ms.date : 04/20/2020
6
6
---
7
7
# Create Resource Manager parameter file
8
8
@@ -14,7 +14,7 @@ The parameter file has the following format:
14
14
15
15
``` json
16
16
{
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#" ,
18
18
"contentVersion" : " 1.0.0.0" ,
19
19
"parameters" : {
20
20
"<first-parameter-name>" : {
@@ -33,7 +33,7 @@ The following parameter file includes a plain text value and a value that is sto
33
33
34
34
``` json
35
35
{
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#" ,
37
37
"contentVersion" : " 1.0.0.0" ,
38
38
"parameters" : {
39
39
"<first-parameter-name>" : {
@@ -80,7 +80,7 @@ The first detail to notice is the name of each parameter. The values in your par
80
80
81
81
``` json
82
82
{
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#" ,
84
84
"contentVersion" : " 1.0.0.0" ,
85
85
"parameters" : {
86
86
"storagePrefix" : {
@@ -95,7 +95,7 @@ Notice the type of the parameter. The values in your parameter file must have th
95
95
96
96
``` json
97
97
{
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#" ,
99
99
"contentVersion" : " 1.0.0.0" ,
100
100
"parameters" : {
101
101
"storagePrefix" : {
@@ -112,7 +112,7 @@ Next, look for a default value. If a parameter has a default value, you can prov
112
112
113
113
``` json
114
114
{
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#" ,
116
116
"contentVersion" : " 1.0.0.0" ,
117
117
"parameters" : {
118
118
"storagePrefix" : {
@@ -129,7 +129,7 @@ Finally, look at the allowed values and any restrictions like max length. They t
129
129
130
130
``` json
131
131
{
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#" ,
133
133
"contentVersion" : " 1.0.0.0" ,
134
134
"parameters" : {
135
135
"storagePrefix" : {
@@ -148,7 +148,7 @@ The following example shows the formats of different parameter types.
148
148
149
149
``` json
150
150
{
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#" ,
152
152
"contentVersion" : " 1.0.0.0" ,
153
153
"parameters" : {
154
154
"exampleString" : {
0 commit comments