Merge pull request #287679 from LiSeda/LS_bicep_batch1

LS_Bicep updates_batch 1

Author: AnnaMHuff

articles/azure-resource-manager/bicep/linter-rule-no-unused-existing-resources.md

@@ -3,7 +3,7 @@ title: Linter rule - no unused existing resources
 description: Linter rule - no unused existing resources
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 07/11/2024
+ms.date: 10/14/2024
 ---
 
 # Linter rule - no unused existing resources
@@ -23,14 +23,14 @@ To reduce confusion in your template, delete any [existing resources](./existing
 The following example fails this test because the existing resource **stg** is declared but never used:
 
 ```bicep
-resource stg 'Microsoft.Storage/storageAccounts@2023-04-01' existing = {
+resource stg 'Microsoft.Storage/storageAccounts@2023-05-01' existing = {
   name: 'examplestorage'
 }
 ```
 
-Use **Quick Fix** to remove the unused existing resource.
+Use **Quick Fix** to remove the unused existing resource:
 
-:::image type="content" source="./media/linter-rule-no-unused-existing-resources/linter-rule-no-unused-existing-resources-quick-fix.png" alt-text="The screenshot of No unused existing resources linter rule quick fix.":::
+:::image type="content" source="./media/linter-rule-no-unused-existing-resources/linter-rule-no-unused-existing-resources-quick-fix.png" alt-text="A screenshot using Quick Fix for the no-unused-existing-resources linter rule.":::
 
 ## Next steps
 

articles/azure-resource-manager/bicep/linter-rule-no-unused-parameters.md

@@ -3,7 +3,7 @@ title: Linter rule - no unused parameters
 description: Linter rule - no unused parameters
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 03/20/2024
+ms.date: 10/14/2024
 ---
 
 # Linter rule - no unused parameters
@@ -18,11 +18,11 @@ Use the following value in the [Bicep configuration file](bicep-config-linter.md
 
 ## Solution
 
-To reduce confusion in your template, delete any parameters that are defined but not used. This test finds any parameters that aren't used anywhere in the template. Eliminating unused parameters also makes it easier to deploy your template because you don't have to provide unnecessary values.
+To reduce confusion in your template, delete any parameters that are defined but not used. This test finds all parameters that aren't used anywhere in the template. Eliminating unused parameters also makes it easier to deploy your template because you don't have to provide unnecessary values.
 
-You can use **Quick Fix** to remove the unused parameters:
+Use **Quick Fix** to remove the unused parameters:
 
-:::image type="content" source="./media/linter-rule-no-unused-parameters/linter-rule-no-unused-parameters-quick-fix.png" alt-text="The screenshot of No unused parameters linter rule quick fix.":::
+:::image type="content" source="./media/linter-rule-no-unused-parameters/linter-rule-no-unused-parameters-quick-fix.png" alt-text="A screenshot of using Quick Fix for the no-unused-parameters linter rule.":::
 
 ## Next steps
 

articles/azure-resource-manager/bicep/linter-rule-no-unused-variables.md

@@ -3,7 +3,7 @@ title: Linter rule - no unused variables
 description: Linter rule - no unused variables
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 03/20/2024
+ms.date: 10/14/2024
 ---
 
 # Linter rule - no unused variables
@@ -18,11 +18,11 @@ Use the following value in the [Bicep configuration file](bicep-config-linter.md
 
 ## Solution
 
-To reduce confusion in your template, delete any variables that are defined but not used. This test finds any variables that aren't used anywhere in the template.
+To reduce confusion in your template, delete any variables that are defined but not used. This test finds all variables that aren't used anywhere in the template.
 
-You can use **Quick Fix** to remove the unused variables:
+Use **Quick Fix** to remove the unused variables:
 
-:::image type="content" source="./media/linter-rule-no-unused-variables/linter-rule-no-unused-variables-quick-fix.png" alt-text="The screenshot of No unused variables linter rule quick fix.":::
+:::image type="content" source="./media/linter-rule-no-unused-variables/linter-rule-no-unused-variables-quick-fix.png" alt-text="A screenshot of using Quick Fix for the no-unused-variables linter rule.":::
 
 ## Next steps
 

articles/azure-resource-manager/bicep/linter-rule-use-parent-property.md

@@ -3,12 +3,12 @@ title: Linter rule - use parent property
 description: Linter rule - use parent property
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 07/11/2024
+ms.date: 10/14/2024
 ---
 
 # Linter rule - use parent property
 
-When defined outside of the parent resource, you use slashes to include the parent name in the name of the child resource. Setting the full resource name with parent resource name is not recommended. The `parent` property can be used to simplify the syntax. See [Full resource name outside parent](./child-resource-name-type.md#full-resource-name-outside-parent).
+When defined outside of the parent resource, you use slashes to include the parent name in the name of the child resource. Defining the full resource name with the parent resource name isn't recommended. The `parent` property can be used to simplify the syntax. See [Full resource name outside parent](./child-resource-name-type.md#full-resource-name-outside-parent).
 
 ## Linter rule code
 
@@ -23,7 +23,7 @@ The following example fails this test because of the name values for `service` a
 ```bicep
 param location string = resourceGroup().location
 
-resource storage 'Microsoft.Storage/storageAccounts@2023-04-01' = {
+resource storage 'Microsoft.Storage/storageAccounts@2023-05-01' = {
   name: 'examplestorage'
   location: location
   kind: 'StorageV2'
@@ -32,14 +32,14 @@ resource storage 'Microsoft.Storage/storageAccounts@2023-04-01' = {
   }
 }
 
-resource service 'Microsoft.Storage/storageAccounts/fileServices@2023-04-01' = {
+resource service 'Microsoft.Storage/storageAccounts/fileServices@2023-05-01' = {
   name: 'examplestorage/default'
   dependsOn: [
     storage
   ]
 }
 
-resource share 'Microsoft.Storage/storageAccounts/fileServices/shares@2023-04-01' = {
+resource share 'Microsoft.Storage/storageAccounts/fileServices/shares@2023-05-01' = {
   name: 'examplestorage/default/exampleshare'
   dependsOn: [
     service
@@ -52,7 +52,7 @@ You can fix the problem by using the `parent` property:
 ```bicep
 param location string = resourceGroup().location
 
-resource storage 'Microsoft.Storage/storageAccounts@2023-04-01' = {
+resource storage 'Microsoft.Storage/storageAccounts@2023-05-01' = {
   name: 'examplestorage'
   location: location
   kind: 'StorageV2'
@@ -61,20 +61,20 @@ resource storage 'Microsoft.Storage/storageAccounts@2023-04-01' = {
   }
 }
 
-resource service 'Microsoft.Storage/storageAccounts/fileServices@2023-04-01' = {
+resource service 'Microsoft.Storage/storageAccounts/fileServices@2023-05-01' = {
   parent: storage
   name: 'default'
 }
 
-resource share 'Microsoft.Storage/storageAccounts/fileServices/shares@2023-04-01' = {
+resource share 'Microsoft.Storage/storageAccounts/fileServices/shares@2023-05-01' = {
   parent: service
   name: 'exampleshare'
 }
 ```
 
-You can fix the issue automatically by selecting **Quick Fix** as shown on the following screenshot:
+Use **Quick Fix** to simplify the syntax:
 
-:::image type="content" source="./media/linter-rule-use-parent-property/bicep-linter-rule-use-parent-property-quick-fix.png" alt-text="Screenshot of use parent property quick fix.":::
+:::image type="content" source="./media/linter-rule-use-parent-property/bicep-linter-rule-use-parent-property-quick-fix.png" alt-text="A screenshot of using Quick Fix for the use-parent-property linter rule.":::
 
 ## Next steps
 

articles/azure-resource-manager/bicep/linter-rule-use-resource-symbol-reference.md

@@ -3,12 +3,12 @@ title: Linter rule - use resource symbol reference
 description: Linter rule - use resource symbol reference
 ms.topic: reference
 ms.custom: devx-track-bicep
-ms.date: 07/11/2024
+ms.date: 10/14/2024
 ---
 
 # Linter rule - use resource symbol reference
 
-This rule detects suboptimal uses of the [`reference`](./bicep-functions-resource.md#reference), and [`list`](./bicep-functions-resource.md#list) functions. Instead of invoking these functions, using a resource reference simplifies the syntax and allows Bicep to better understand your deployment dependency graph.
+This rule detects suboptimal uses of the [`reference`](./bicep-functions-resource.md#reference) and [`list`](./bicep-functions-resource.md#list) functions. Instead of invoking these functions, using a resource reference simplifies the syntax and allows Bicep to better understand your deployment dependency graph.
 
 ## Linter rule code
 
@@ -27,7 +27,7 @@ param clusterName string
 @description('These credentials can be used to submit jobs to the cluster and to log into cluster dashboards.')
 param clusterLoginUserName string
 
-@description('The password must be at least 10 characters in length and must contain at least one digit, one upper case letter, one lower case letter, and one non-alphanumeric character except (single-quote, double-quote, backslash, right-bracket, full-stop). Also, the password must not contain 3 consecutive characters from the cluster username or SSH username.')
+@description('The password must be at least 10 characters in length and must contain at least one digit, one uppercase letter, one lowercase letter, and one non-alphanumeric character (except single-quote, double-quote, backslash, right-bracket, or full-stop characters). Also, the password must not contain three consecutive characters from the cluster username or SSH username.')
 @minLength(10)
 @secure()
 param clusterLoginPassword string
@@ -37,11 +37,11 @@ param location string = resourceGroup().location
 
 param storageAccountName string = uniqueString(resourceGroup().id)
 
-resource storageAccount 'Microsoft.Storage/storageAccounts@2023-04-01' existing = {
+resource storageAccount 'Microsoft.Storage/storageAccounts@2023-05-01' existing = {
   name: storageAccountName
 }
 
-resource cluster 'Microsoft.HDInsight/clusters@2023-08-15-preview' = {
+resource cluster 'Microsoft.HDInsight/clusters@2024-08-01-preview' = {
   name: clusterName
   location: location
   properties: {
@@ -60,10 +60,10 @@ resource cluster 'Microsoft.HDInsight/clusters@2023-08-15-preview' = {
     storageProfile: {
       storageaccounts: [
         {
-          name: replace(replace(reference(storageAccount.id, '2023-04-01').primaryEndpoints.blob, 'https://', ''), '/', '')
+          name: replace(replace(reference(storageAccount.id, '2023-05-01').primaryEndpoints.blob, 'https://', ''), '/', '')
           isDefault: true
           container: clusterName
-          key: listKeys(storageAccount.id, '2023-04-01').keys[0].value
+          key: listKeys(storageAccount.id, '2023-05-01').keys[0].value
         }
       ]
     }
@@ -80,7 +80,7 @@ param clusterName string
 @description('These credentials can be used to submit jobs to the cluster and to log into cluster dashboards.')
 param clusterLoginUserName string
 
-@description('The password must be at least 10 characters in length and must contain at least one digit, one upper case letter, one lower case letter, and one non-alphanumeric character except (single-quote, double-quote, backslash, right-bracket, full-stop). Also, the password must not contain 3 consecutive characters from the cluster username or SSH username.')
+@description('The password must be at least 10 characters in length and must contain at least one digit, one uppercase letter, one lowercase letter, and one non-alphanumeric character (except single-quote, double-quote, backslash, right-bracket, or full-stop characters). Also, the password must not contain three consecutive characters from the cluster username or SSH username.')
 @minLength(10)
 @secure()
 param clusterLoginPassword string
@@ -90,11 +90,11 @@ param location string = resourceGroup().location
 
 param storageAccountName string = uniqueString(resourceGroup().id)
 
-resource storageAccount 'Microsoft.Storage/storageAccounts@2023-04-01' existing = {
+resource storageAccount 'Microsoft.Storage/storageAccounts@2023-05-01' existing = {
   name: storageAccountName
 }
 
-resource cluster 'Microsoft.HDInsight/clusters@2023-08-15-preview' = {
+resource cluster 'Microsoft.HDInsight/clusters@2024-08-01-preview' = {
   name: clusterName
   location: location
   properties: {
@@ -124,9 +124,9 @@ resource cluster 'Microsoft.HDInsight/clusters@2023-08-15-preview' = {
 }
 ```
 
-You can fix the issue automatically by selecting **Quick Fix** as shown on the following screenshot:
+Use **Quick Fix** to simplify the syntax:
 
-:::image type="content" source="./media/linter-rule-use-resource-symbol-reference/bicep-linter-rule-use-resource-symbol-reference-quick-fix.png" alt-text="Screenshot of use resource symbol reference quick fix." lightbox="./media/linter-rule-use-resource-symbol-reference/bicep-linter-rule-use-resource-symbol-reference-quick-fix.png":::
+:::image type="content" source="./media/linter-rule-use-resource-symbol-reference/bicep-linter-rule-use-resource-symbol-reference-quick-fix.png" alt-text="A screenshot of using Quick fix for the use-resource-symbol-reference linter rule." lightbox="./media/linter-rule-use-resource-symbol-reference/bicep-linter-rule-use-resource-symbol-reference-quick-fix.png":::
 
 ## Next steps