Skip to content

Commit 42f8c54

Browse files
authored
Update author-global-parameters.md
1 parent 5688f56 commit 42f8c54

File tree

1 file changed

+4
-5
lines changed

1 file changed

+4
-5
lines changed

articles/data-factory/author-global-parameters.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -38,14 +38,15 @@ Global parameters can be used in any [pipeline expression](control-flow-expressi
3838

3939
## <a name="cicd"></a> Global parameters in CI/CD
4040

41-
We recommend including global parameters in the ARM template during the CI/CD. The new mechanism of including global parameters in the ARM template (from 'Manage hub' -> 'ARM template' -> ‘Include global parameters in ARM template
42-
') as illustrated below, will not conflict/ override the factory-level settings as it used to do earlier, hence not requiring additional PowerShell for global parameters deployment during CI/CD.
41+
We recommend including global parameters in the ARM template during the CI/CD. The new mechanism of including global parameters in the ARM template (from 'Manage hub' -> 'ARM template' -> ‘Include global parameters in ARM template') as illustrated below, will not conflict/ override the factory-level settings as it used to do earlier, hence not requiring additional PowerShell for global parameters deployment during CI/CD.
4342

4443
:::image type="content" source="media/author-global-parameters/include-arm-template.png" alt-text="Screenshot of 'Include in ARM template'.":::
4544

4645
> [!NOTE]
4746
> We have moved the UI experience for including global parameters from the 'Global parameters' section to the 'ARM template' section in the manage hub.
48-
If you are already using the older mechanism (from 'Manage hub' -> 'Global parameters' -> 'Include in ARM template'), you can continue. We will continue to support it.
47+
If you are already using the older mechanism (from 'Manage hub' -> 'Global parameters' -> 'Include in ARM template'), you can continue. We will continue to support it.
48+
49+
The **Parameters** folder in the downloaded ARM template contains JSON files that define the parameters used in the ARM template. Each file corresponds to a specific global parameter.
4950

5051
If you are using the older flow of integrating global parameters in your continuous integration and deployment solution, it will continue to work:
5152

@@ -62,8 +63,6 @@ We strongly recommend using the new mechanism of including global parameters in
6263
> [!WARNING]
6364
>You cannot use ‘-‘ in the parameter name. You will receive an errorcode "{"code":"BadRequest","message":"ErrorCode=InvalidTemplate,ErrorMessage=The expression >'pipeline().globalParameters.myparam-dbtest-url' is not valid: .....}". But, you can use the ‘_’ in the parameter name.
6465
65-
66-
6766
## Related content
6867

6968
* Learn about Azure Data Factory's [continuous integration and deployment process](continuous-integration-delivery-improvements.md)

0 commit comments

Comments
 (0)