Skip to content

Commit 1c4e94b

Browse files
Small updates (#3044)
1 parent 6274715 commit 1c4e94b

3 files changed

Lines changed: 5 additions & 5 deletions

File tree

docs/wiki/Getting started - Scenario 1 Consume library.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -70,7 +70,7 @@ If you are not using a local repository, you'll also need to publish the modules
7070
The preferred method to publish modules to template-specs is to leverage CARML ready [CI environment](./The%20CI%20environment), however there maybe specific requirements for which this option is not applicable. As an alternative, the same [Publish-ModuleToTemplateSpecsRG.ps1](https://github.com/Azure/ResourceModules/blob/main/utilities/pipelines/resourcePublish/Publish-ModuleToPrivateBicepRegistry.ps1) script leveraged by the publishing step of the CI environment pipeline can be executed locally.
7171
7272
To publish a module by running the script:
73-
1. Let's suppose your updated library location is `'D:\ResourcesModules'`, open a Powershell session on your machine
73+
1. Let's suppose your updated library location is `'D:\ResourcesModules'`, open a PowerShell session on your machine
7474
1. Navigate to `'D:\ResourcesModules\utilities\pipelines\resourcePublish'` location
7575
1. Load the script `'Publish-ModuleToTemplateSpecsRG.ps1'` executing:
7676
@@ -111,7 +111,7 @@ To publish a module by running the script:
111111
The preferred method to publish modules to Bicep Registry is to leverage CARML ready [CI environment](./The%20CI%20environment), however there maybe specific requirements for which this option is not applicable. As an alternative, the same [Publish-ModuleToPrivateBicepRegistry.ps1](https://github.com/Azure/ResourceModules/blob/main/utilities/pipelines/resourcePublish/Publish-ModuleToPrivateBicepRegistry.ps1) script leveraged by the publishing step of the CI environment pipeline can be executed locally.
112112
113113
To publish a module by running the script:
114-
1. Let's suppose your updated library location is `'D:\ResourcesModules'`, open a Powershell session on your machine
114+
1. Let's suppose your updated library location is `'D:\ResourcesModules'`, open a PowerShell session on your machine
115115
1. Navigate to `'D:\ResourcesModules\utilities\pipelines\resourcePublish'` location
116116
1. Load the script `'Publish-ModuleToPrivateBicepRegistry.ps1'` executing:
117117
@@ -150,7 +150,7 @@ To publish a module by running the script:
150150
The preferred method to publish modules to Azure DevOps artifact feed is to leverage CARML ready [CI environment](./The%20CI%20environment), however there maybe specific requirements for which this option is not applicable. As an alternative, the same [Publish-ModuleToUniversalArtifactsFeed.ps1](https://github.com/Azure/ResourceModules/blob/main/utilities/pipelines/resourcePublish/Publish-ModuleToUniversalArtifactsFeed.ps1) script leveraged by the publishing step of the CI environment pipeline can be executed locally.
151151
152152
To publish a module by running the script:
153-
1. Let's suppose your updated library location is `'D:\ResourcesModules'`, open a Powershell session on your machine
153+
1. Let's suppose your updated library location is `'D:\ResourcesModules'`, open a PowerShell session on your machine
154154
1. Navigate to `'D:\ResourcesModules\utilities\pipelines\resourcePublish'` location
155155
1. Load the script `'Publish-ModuleToUniversalArtifactsFeed.ps1'` executing:
156156

modules/Microsoft.Insights/activityLogAlerts/deploy.bicep

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ param location string = 'global'
1010
@description('Optional. Indicates whether this alert is enabled.')
1111
param enabled bool = true
1212

13-
@description('Optional. The list of resource IDs that this metric alert is scoped to.')
13+
@description('Optional. The list of resource IDs that this Activity Log Alert is scoped to.')
1414
param scopes array = [
1515
subscription().id
1616
]

modules/Microsoft.Insights/activityLogAlerts/readme.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ This module deploys an Alert based on Activity Log.
3636
| `enableDefaultTelemetry` | bool | `True` | Enable telemetry via a Globally Unique Identifier (GUID). |
3737
| `location` | string | `'global'` | Location for all resources. |
3838
| `roleAssignments` | array | `[]` | Array of role assignment objects that contain the 'roleDefinitionIdOrName' and 'principalId' to define RBAC role assignments on this resource. In the roleDefinitionIdOrName attribute, you can provide either the display name of the role definition, or its fully qualified ID in the following format: '/providers/Microsoft.Authorization/roleDefinitions/c2f4ef07-c644-48eb-af81-4b1b4947fb11'. |
39-
| `scopes` | array | `[[subscription().id]]` | The list of resource IDs that this metric alert is scoped to. |
39+
| `scopes` | array | `[[subscription().id]]` | The list of resource IDs that this Activity Log Alert is scoped to. |
4040
| `tags` | object | `{object}` | Tags of the resource. |
4141

4242

0 commit comments

Comments
 (0)