Merge pull request #203538 from mumian/0511-bicep-restore

explain restore by force

Author: PRMerger20

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

@@ -2,7 +2,7 @@
 title: Bicep CLI commands and overview
 description: Describes the commands that you can use in the Bicep CLI. These commands include building Azure Resource Manager templates from Bicep.
 ms.topic: conceptual
-ms.date: 03/15/2022
+ms.date: 06/30/2022
 ---
 
 # Bicep CLI commands
@@ -41,6 +41,9 @@ az bicep build --file main.bicep --stdout
 
 If your Bicep file includes a module that references an external registry, the build command automatically calls [restore](#restore). The restore command gets the file from the registry and stores it in the local cache.
 
+> [!NOTE]
+> The restore command doesn't refresh the cache. For more information, see [restore](#restore).
+
 To not call restore automatically, use the `--no-restore` switch:
 
 ```azurecli
@@ -149,7 +152,7 @@ To use the restore command, you must have Bicep CLI version **0.4.1008 or later*
 To manually restore the external modules for a file, use:
 
 ```powershell
-bicep restore <bicep-file>
+bicep restore <bicep-file> [--force]
 ```
 
 The Bicep file you provide is the file you wish to deploy. It must contain a module that links to a registry. For example, you can restore the following file:
@@ -177,6 +180,8 @@ The local cache is found in:
     /home/<username>/.bicep
     ```
 
+The `restore` command doesn't refresh the cache if a module is already cached. To fresh the cache, you can either delete the module path from the cache or use the `--force` switch with the `restore` command.
+
 ## upgrade
 
 The `upgrade` command updates your installed version with the latest version. This command is only available through Azure CLI.