You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/wiki/Getting started - Scenario 1 Consume library.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -70,7 +70,7 @@ If you are not using a local repository, you'll also need to publish the modules
70
70
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.
71
71
72
72
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
74
74
1. Navigate to `'D:\ResourcesModules\utilities\pipelines\resourcePublish'` location
75
75
1. Load the script `'Publish-ModuleToTemplateSpecsRG.ps1'` executing:
76
76
@@ -111,7 +111,7 @@ To publish a module by running the script:
111
111
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.
112
112
113
113
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
115
115
1. Navigate to `'D:\ResourcesModules\utilities\pipelines\resourcePublish'` location
116
116
1. Load the script `'Publish-ModuleToPrivateBicepRegistry.ps1'` executing:
117
117
@@ -150,7 +150,7 @@ To publish a module by running the script:
150
150
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.
151
151
152
152
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
154
154
1. Navigate to `'D:\ResourcesModules\utilities\pipelines\resourcePublish'` location
155
155
1. Load the script `'Publish-ModuleToUniversalArtifactsFeed.ps1'` executing:
Copy file name to clipboardExpand all lines: modules/Microsoft.Insights/activityLogAlerts/readme.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,7 @@ This module deploys an Alert based on Activity Log.
36
36
|`enableDefaultTelemetry`| bool |`True`| Enable telemetry via a Globally Unique Identifier (GUID). |
37
37
|`location`| string |`'global'`| Location for all resources. |
38
38
|`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. |
40
40
|`tags`| object |`{object}`| Tags of the resource. |
0 commit comments