This post has been republished via RSS; it originally appeared at: Microsoft Tech Community - Latest Blogs - .
We are introducing a new mechanism to include Global parameters in the ARM templates (from 'Manage hub' ->' ARM template' -> 'Include global parameters in ARM template').
It solves the earlier known issue, which overrode some Data Factory level configurations during deployments if the global parameters were included in the ARM template (from 'Manage hub' -> 'Global parameters' -> 'Include in ARM template'). Hence, earlier in such scenarios, we recommended using PowerShell to deploy global parameters and not include them in the ARM template. It resulted in a complex release process.
Note:
- The change breaks any existing release pipelines you may have for deploying the global parameters (using PowerShell). It is transparent to existing CICD pipelines.
- If you deployed the global parameters through the ARM template using the older mechanism (from 'Manage hub' -> 'Global parameters' -> 'Include in ARM template').
- All new setups should include global parameters in the ARM template using the more recent mechanism (from 'Manage hub' ->' ARM template' -> 'Include global parameters in ARM template').
- The @microsoft/azure-data-factory-utilities npm package for automated deployments is also compatible with the new mechanism for deploying global parameters across environments.
Reference:
Global parameters - Azure Data Factory | Microsoft Docs