Skip to content

Commit

Permalink
Small updates (#3044)
Browse files Browse the repository at this point in the history
  • Loading branch information
AlexanderSehr authored Mar 23, 2023
1 parent 6274715 commit 1c4e94b
Show file tree
Hide file tree
Showing 3 changed files with 5 additions and 5 deletions.
6 changes: 3 additions & 3 deletions docs/wiki/Getting started - Scenario 1 Consume library.md
Original file line number Diff line number Diff line change
Expand Up @@ -70,7 +70,7 @@ If you are not using a local repository, you'll also need to publish the modules
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.
To publish a module by running the script:
1. Let's suppose your updated library location is `'D:\ResourcesModules'`, open a Powershell session on your machine
1. Let's suppose your updated library location is `'D:\ResourcesModules'`, open a PowerShell session on your machine
1. Navigate to `'D:\ResourcesModules\utilities\pipelines\resourcePublish'` location
1. Load the script `'Publish-ModuleToTemplateSpecsRG.ps1'` executing:
Expand Down Expand Up @@ -111,7 +111,7 @@ To publish a module by running the script:
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.
To publish a module by running the script:
1. Let's suppose your updated library location is `'D:\ResourcesModules'`, open a Powershell session on your machine
1. Let's suppose your updated library location is `'D:\ResourcesModules'`, open a PowerShell session on your machine
1. Navigate to `'D:\ResourcesModules\utilities\pipelines\resourcePublish'` location
1. Load the script `'Publish-ModuleToPrivateBicepRegistry.ps1'` executing:
Expand Down Expand Up @@ -150,7 +150,7 @@ To publish a module by running the script:
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.
To publish a module by running the script:
1. Let's suppose your updated library location is `'D:\ResourcesModules'`, open a Powershell session on your machine
1. Let's suppose your updated library location is `'D:\ResourcesModules'`, open a PowerShell session on your machine
1. Navigate to `'D:\ResourcesModules\utilities\pipelines\resourcePublish'` location
1. Load the script `'Publish-ModuleToUniversalArtifactsFeed.ps1'` executing:
Expand Down
2 changes: 1 addition & 1 deletion modules/Microsoft.Insights/activityLogAlerts/deploy.bicep
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ param location string = 'global'
@description('Optional. Indicates whether this alert is enabled.')
param enabled bool = true

@description('Optional. The list of resource IDs that this metric alert is scoped to.')
@description('Optional. The list of resource IDs that this Activity Log Alert is scoped to.')
param scopes array = [
subscription().id
]
Expand Down
2 changes: 1 addition & 1 deletion modules/Microsoft.Insights/activityLogAlerts/readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -36,7 +36,7 @@ This module deploys an Alert based on Activity Log.
| `enableDefaultTelemetry` | bool | `True` | Enable telemetry via a Globally Unique Identifier (GUID). |
| `location` | string | `'global'` | Location for all resources. |
| `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'. |
| `scopes` | array | `[[subscription().id]]` | The list of resource IDs that this metric alert is scoped to. |
| `scopes` | array | `[[subscription().id]]` | The list of resource IDs that this Activity Log Alert is scoped to. |
| `tags` | object | `{object}` | Tags of the resource. |


Expand Down

0 comments on commit 1c4e94b

Please # to comment.