Skip to content

Commit 2c6d44d

Browse files
Merge pull request #291551 from LiSeda/LS-params4
LS_Bicep parameters_batch 4
2 parents eebc42b + d213e75 commit 2c6d44d

File tree

2 files changed

+8
-8
lines changed

2 files changed

+8
-8
lines changed

articles/azure-resource-manager/bicep/template-specs.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Create & deploy template specs in Bicep
33
description: Describes how to create template specs in Bicep and share them with other users in your organization.
44
ms.topic: how-to
55
ms.custom: devx-track-azurepowershell, devx-track-azurecli, devx-track-arm-template, devx-track-bicep
6-
ms.date: 09/26/2024
6+
ms.date: 12/06/2024
77
---
88

99
# Azure Resource Manager template specs in Bicep
@@ -268,7 +268,7 @@ https://portal.azure.com/#create/Microsoft.Template/templateSpecVersionId/%2fsub
268268

269269
## Parameters
270270

271-
Passing in parameters to template spec is similar to passing parameters to a Bicep file. Add the parameter values either inline or in a parameter file.
271+
Passing in parameters to template spec is similar to passing parameters to a Bicep file. Add the parameter values either inline or in a parameters file.
272272

273273
### Inline parameters
274274

@@ -294,11 +294,11 @@ az deployment group create \
294294

295295
---
296296

297-
### Parameter files
297+
### Parameters files
298298

299299
- Use Bicep parameters file
300300

301-
To create a Bicep parameter file, you must specify the `using` statement. Here's an example:
301+
To create a Bicep parameters file, you must specify the `using` statement. Here's an example:
302302

303303
```bicep
304304
using 'using 'ts:<subscription-id>/<resource-group-name>/<template-spec-name>:<tag>'
@@ -308,7 +308,7 @@ az deployment group create \
308308
309309
For more information, see [Bicep parameters file](./parameter-files.md).
310310
311-
To pass parameter file with:
311+
To pass parameters file with:
312312
313313
# [PowerShell](#tab/azure-powershell)
314314
@@ -342,7 +342,7 @@ az deployment group create \
342342
}
343343
```
344344
345-
And, pass that parameter file with:
345+
And, pass that parameters file with:
346346
347347
# [PowerShell](#tab/azure-powershell)
348348

articles/azure-resource-manager/bicep/visual-studio-code.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Create Bicep files by using Visual Studio Code
33
description: Learn how to use Visual Studio Code to create Bicep files.
44
ms.topic: how-to
55
ms.custom: devx-track-bicep
6-
ms.date: 11/20/2024
6+
ms.date: 12/06/2024
77
---
88

99
# Create Bicep files by using Visual Studio Code
@@ -78,7 +78,7 @@ You can deploy Bicep files directly from Visual Studio Code. Select **Deploy Bic
7878

7979
### Generate parameters file
8080

81-
This command creates a parameter file in the same folder as the Bicep file. You can choose to create a Bicep parameter file or a JSON parameter file. The new Bicep parameter file name is `<bicep-file-name>.bicepparam`, while the new JSON parameter file name is `<bicep-file-name>.parameters.json`.
81+
This command creates a parameters file in the same folder as the Bicep file. You can choose to create a Bicep parameters file or a JSON parameters file. The new Bicep parameters file name is `<bicep-file-name>.bicepparam`, while the new JSON parameters file name is `<bicep-file-name>.parameters.json`.
8282

8383
### Import Kubernetes manifest (Preview)
8484

0 commit comments

Comments
 (0)