Skip to content

Commit 8d0f42d

Browse files
update custom deploy logic for bicepparam files
1 parent d054f24 commit 8d0f42d

File tree

2 files changed

+252
-5
lines changed

2 files changed

+252
-5
lines changed

articles/sentinel/ci-cd-custom-deploy.md

Lines changed: 13 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -164,21 +164,29 @@ For more information, see the [Azure DevOps documentation](/azure/devops/pipelin
164164
165165
## Scale your deployments with parameter files
166166
167-
Rather than passing parameters as inline values in your content files, consider [using a JSON file that contains the parameter values](../azure-resource-manager/templates/parameter-files.md). Then map those parameter JSON files to their associated Sentinel content files to better scale your deployments across different workspaces. There are several ways to map parameter files to Sentinel files, and the repositories deployment pipeline considers them in the following order:
167+
Rather than passing parameters as inline values in your content files, consider [using a Bicep parameter file](../azure-resource-manager/bicep/parameter-files.md) or a [JSON file that contains the parameter values](../azure-resource-manager/templates/parameter-files.md). Then map those parameter files to their associated Sentinel content files to better scale your deployments across different workspaces. There are several ways to map parameter files to Sentinel files, and the repositories deployment pipeline considers them in the following order:
168168
169-
:::image type="content" source="media/ci-cd-custom-deploy/deploy-parameter-file-precedence.svg" alt-text="A diagram showing the precedence of parameter file mappings.":::
169+
:::image type="content" source="media/ci-cd-custom-deploy/deploy-parameter-file-precedence-with-bicep.svg" alt-text="A diagram showing the precedence of parameter file mappings.":::
170170
171171
1. Is there a mapping in the *sentinel-deployment.config*? For more information, see [Customize your connection configuration](ci-cd-custom-deploy.md#customize-your-connection-configuration).
172-
1. Is there a workspace-mapped parameter file? Yes it's a parameter file in the same directory as the content files that ends with *.parameters-\<WorkspaceID>.json*
173-
1. Is there a default parameter file? Yes, any parameter file in the same directory as the content files that ends with *.parameters.json*
172+
1. Is there a workspace-mapped parameter file? Yes, it's a parameter file in the same directory as the content files that ends with *.\<WorkspaceID>.bicepparam* or *.parameters-\<WorkspaceID>.json*
173+
1. Is there a default parameter file? Yes, any parameter file in the same directory as the content files that ends with *.bicepparam* or *.parameters.json*
174174
175175
It's encouraged to map your parameter files through the configuration file or by specifying the workspace ID in the file name to avoid clashes in scenarios with multiple deployments.
176176
177177
> [!IMPORTANT]
178178
> Once a parameter file match is determined based on the mapping precedence, the pipeline ignores any remaining mappings.
179179
>
180180
181-
Modifying the mapped parameter file listed in the sentinel-deployment.config triggers the deployment of its paired content file. Adding or modifying a *.parameters-\<WorkspaceID\>.json* file or *.parameters.json* file also triggers a deployment of the paired content files along with the newly modified parameters, unless a higher precedence parameter mappings is in place. Other content files aren't deployed as long as the smart deployments feature is still enabled in the workflow/pipeline definition file.
181+
Modifying the mapped parameter file listed in the sentinel-deployment.config triggers the deployment of its paired content file. Adding or modifying a workspace-mapped parameter file or a default parameter file also triggers a deployment of the paired content files along with the newly modified parameters, unless a higher precedence parameter mappings is in place. Other content files aren't deployed as long as the smart deployments feature is still enabled in the workflow/pipeline definition file.
182+
183+
Examples of workspace-mapped parameter files:
184+
- *.\<WorkspaceID>.bicepparam*
185+
- *.parameters-\<WorkspaceID\>.json*
186+
187+
Examples of default parameter files:
188+
- *.bicepparam*
189+
- *.parameters.json*
182190
183191
## Customize your connection configuration
184192
Lines changed: 239 additions & 0 deletions
Loading

0 commit comments

Comments
 (0)