Skip to content

Commit a8c874c

Browse files
authored
Update ci-cd-custom-deploy.md
1 parent 615ac2a commit a8c874c

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -162,11 +162,11 @@ Rather than passing parameters as inline values in your content files, you can [
162162
163163
:::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.":::
164164
165-
1. Is there a mapping in the sentinel-deployment.config?
166-
1. Is there a workspace parameter file?
167-
1. Is there a default parameter file?
165+
1. Is there a mapping in the sentinel-deployment.config? [Customize your connection configuration](ci-cd-custom-deploy.md#scale-your-deployments-with-parameter-files) to learn more.
166+
1. Is there a workspace-mapped parameter file? This would be a parameter file in the same directory as the content files that ends with .parameters-<WorkspaceID>.json
167+
1. Is there a default parameter file? This would be any parameter file in the same directory as the content files that ends with .parameters.json
168168
169-
It's important to note that once a parameter file match is determined based on the above mapping precedence, the pipeline will ignore any remaining mappings.
169+
It's important to note that once a parameter file match is determined based on the above mapping precedence, the pipeline will ignore any remaining mappings. It is highly encouraged to map your parameter files through thrrough the configuration file or by specifying the workspace ID in the file name to avoid content clashes in scenarios with multiple deployments.
170170
171171
Modifying the mapped parameter file listed in the sentinel-deployment.config will trigger the deployment of its paired content file. Adding or modifying a *.parameters-\<workspaceID\>.json* file or *.parameters.json* file will also trigger a deployment of the paired content file(s) along with the newly modified parameters, unless a higher precedence parameter mappings is in place. Other content files won't be deployed as long as the smart deployments feature is still enabled in the workflow/pipeline definition file.
172172

0 commit comments

Comments
 (0)