Skip to content

Commit 86b098a

Browse files
committed
updates2
1 parent 1dfaa2a commit 86b098a

File tree

4 files changed

+9
-9
lines changed

4 files changed

+9
-9
lines changed

articles/azure-resource-manager/bicep/deploy-cli.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Deploy Bicep files with the Azure CLI
33
description: Learn how to use Azure Resource Manager and the Azure CLI to deploy resources to Azure. The resources are defined in a Bicep file.
44
ms.topic: how-to
5-
ms.date: 01/06/2025
5+
ms.date: 01/10/2025
66
ms.custom: devx-track-azurecli, seo-azure-cli, devx-track-arm-template, devx-track-bicep
77
---
88

articles/azure-resource-manager/bicep/deploy-powershell.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Deploy Bicep files with Azure PowerShell
33
description: Use Azure Resource Manager and Azure PowerShell to deploy resources to Azure. The resources are defined in a Bicep file.
44
ms.topic: how-to
5-
ms.date: 01/06/2025
5+
ms.date: 01/10/2025
66
ms.custom: devx-track-arm-template, devx-track-bicep, devx-track-azurepowershell
77
---
88

articles/azure-resource-manager/bicep/diagnostics/bcp338.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
11
---
2-
title: Bicep diagnostic code - BCP338
3-
description: Understand the, "Failed to evaluate parameter <parameter-name>," error.
2+
title: BCP338
3+
description: Failed to evaluate parameter <parameter-name>.
44
ms.topic: reference
5-
ms.date: 01/06/2025
5+
ms.date: 01/10/2025
66
ms.custom: devx-track-bicep
77
---
88

9-
# Bicep diagnostic code - BCP338
9+
# BCP338
1010

1111
This diagnostic occurs when Bicep can't resolve a parameter name in a Bicep parameters file.
1212

@@ -24,14 +24,14 @@ Check the value of the parameter.
2424

2525
## Examples
2626

27-
The following _main.bicep_ Bicep parameters file produces the error because the 'testEnvironmentVariable' environment variable can't be found:
27+
The following Bicep parameters file produces the error because the 'testEnvironmentVariable' environment variable can't be found:
2828

2929
```bicep
3030
using 'main.bicep'
3131
param parTest = readEnvironmentVariable('testEnvironmentVariable')
3232
```
3333

34-
It could be because the environment variable isn't defined at the user or system level. You can fix the error by assigning a string whose length is within the allowable range. For more information, see the [`readEnvironmentVariable()` function](../bicep-functions-parameters-file.md#readenvironmentvariable).
34+
It could be because the environment variable isn't defined at the user or system level. For more information, see the [`readEnvironmentVariable()` function](../bicep-functions-parameters-file.md#readenvironmentvariable).
3535

3636
## Next steps
3737

articles/azure-resource-manager/bicep/key-vault-parameter.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
title: Use Azure Key Vault to pass a secret from a key vault as a parameter during Bicep deployment
33
description: Learn how to to pass a secret from a key vault as a parameter during Bicep deployment.
44
ms.topic: conceptual
5-
ms.date: 01/06/2025
5+
ms.date: 01/10/2025
66
ms.custom: devx-track-azurepowershell, devx-track-azurecli, devx-track-bicep
77
---
88

0 commit comments

Comments
 (0)