Skip to content

Commit c0c37b1

Browse files
committed
update the required bicep cli version
1 parent f1f642c commit c0c37b1

File tree

2 files changed

+4
-4
lines changed

2 files changed

+4
-4
lines changed

articles/azure-resource-manager/bicep/private-module-registry.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Create private registry for Bicep module
33
description: Learn how to set up an Azure container registry for private Bicep modules
44
ms.topic: conceptual
55
ms.custom: devx-track-bicep
6-
ms.date: 05/02/2024
6+
ms.date: 05/10/2024
77
---
88

99
# Create private registry for Bicep modules
@@ -73,7 +73,7 @@ az bicep publish --file storage.bicep --target br:exampleregistry.azurecr.io/bic
7373

7474
---
7575

76-
With Azure PowerShell version 11.6 and Azure CLI version xxxx, you can publish a module with the Bicep source code in addition to the compiled JSON template. If a module is published with the Bicep source code to a registry, you can press `F12` ([Go to Definition](./visual-studio-code.md#go-to-definition)) from Visual Studio Code to see the Bicep Code. The Bicep extension version 0.27 or new is required to see the Bicep file.
76+
With Bicep CLI version 0.27.1 or newer, you can publish a module with the Bicep source code in addition to the compiled JSON template. If a module is published with the Bicep source code to a registry, you can press `F12` ([Go to Definition](./visual-studio-code.md#go-to-definition)) from Visual Studio Code to see the Bicep Code. The Bicep extension version 0.27 or new is required to see the Bicep file.
7777

7878
# [PowerShell](#tab/azure-powershell)
7979

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: Describes how to create Bicep files by using Visual Studio Code
44
ms.topic: conceptual
55
ms.custom: devx-track-bicep
6-
ms.date: 05/02/2024
6+
ms.date: 05/10/2024
77
---
88

99
# Create Bicep files by using Visual Studio Code
@@ -127,7 +127,7 @@ From Visual Studio Code, you can open the template reference for the resource ty
127127

128128
## Go to definition
129129

130-
When defining a [module](./modules.md), regardless of the types of the referenced file - whether it is a local file, module registry file, template spec, you can open the referenced file by selecting or highlighting the module path and then press **[F12]**. If the referenced file is an [Azure Verified Modules(AVM)](https://aka.ms/avm), you can toggle between compiled JSON or Bicep file. To be able to open the Bicep file of a private registry module, ensure that the module is published to the registry with the `WithSource` switch enabled. For more information, see [Publish files to registry](./private-module-registry.md#publish-files-to-registry). The Visual Studio Code Bicep extension version 0.27 is required for opening Bicep file from private module registry.
130+
When defining a [module](./modules.md), regardless of the types of the referenced file - whether it is a local file, module registry file, template spec, you can open the referenced file by selecting or highlighting the module path and then press **[F12]**. If the referenced file is an [Azure Verified Modules(AVM)](https://aka.ms/avm), you can toggle between compiled JSON or Bicep file. To be able to open the Bicep file of a private registry module, ensure that the module is published to the registry with the `WithSource` switch enabled. For more information, see [Publish files to registry](./private-module-registry.md#publish-files-to-registry). The Visual Studio Code Bicep extension version 0.27.1 or newer is required for opening Bicep file from private module registry.
131131

132132
## Paste as Bicep
133133

0 commit comments

Comments
 (0)