You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
b. Create a new task. Search for **ARM Template Deployment**, and then select **Add**.
54
+
1. Create a new task. Search for **ARM Template Deployment**, and then select **Add**.
55
55
56
-
c. In the Deployment task, select the subscription, resource group, and location for the target data factory. Provide credentials if necessary.
56
+
1. In the Deployment task, select the subscription, resource group, and location for the target data factory. Provide credentials if necessary.
57
57
58
-
d. In the **Action** list, select **Create or update resource group**.
58
+
1. In the **Action** list, select **Create or update resource group**.
59
59
60
-
e. Select the ellipsis button (**…**) next to the **Template** box. Browse for the Azure Resource Manager template that is generated in your publish branch of the configured git repository. Look for the file `ARMTemplateForFactory.json` in the <FactoryName> folder of the adf_publish branch.
60
+
1.Select the ellipsis button (**…**) next to the **Template** box. Browse for the Azure Resource Manager template that is generated in your publish branch of the configured git repository. Look for the file `ARMTemplateForFactory.json` in the <FactoryName> folder of the adf_publish branch. For more details about using linked ARM templates, see [Deploying linked ARM templates with VSTS](/archive/blogs/najib/deploying-linked-arm-templates-with-vsts) and [Using linked templates](continuous-integration-delivery-linked-templates.md#using-linked-templates).
61
61
62
-
# MS CSS got many support cases that except the maximum size limitation of ARM template
1. Select **…** next to the **Template parameters** box to choose the parameters file. Look for the file `ARMTemplateParametersForFactory.json` in the >FactoryName< folder of the adf_publish branch.
66
63
67
-
f. Select **…** next to the **Template parameters** box to choose the parameters file. Look for the file `ARMTemplateParametersForFactory.json` in the >FactoryName< folder of the adf_publish branch.
64
+
1.Select **…** next to the **Override template parameters** box, and enter the desired parameter values for the target data factory. For credentials that come from Azure Key Vault, enter the secret's name between double quotation marks. For example, if the secret's name is cred1, enter **"$(cred1)"** for this value.
68
65
69
-
g. Select **…** next to the **Override template parameters** box, and enter the desired parameter values for the target data factory. For credentials that come from Azure Key Vault, enter the secret's name between double quotation marks. For example, if the secret's name is cred1, enter **"$(cred1)"** for this value.
66
+
1.Select **Incremental**for the **Deployment mode**.
70
67
71
-
h. Select **Incremental** for the **Deployment mode**.
68
+
> [!WARNING]
69
+
> In Complete deployment mode, resources that exist in the resource group but aren't specified in the new Resource Manager template will be **deleted**. For more information, please refer to [Azure Resource Manager Deployment Modes](../azure-resource-manager/templates/deployment-modes.md)
72
70
73
-
> [!WARNING]
74
-
> In Complete deployment mode, resources that exist in the resource group but aren't specified in the new Resource Manager template will be **deleted**. For more information, please refer to [Azure Resource Manager Deployment Modes](../azure-resource-manager/templates/deployment-modes.md)
1. To trigger a release, select **Create release**. To automate the creation of releases, see [Azure DevOps release triggers](/azure/devops/pipelines/release/triggers)
0 commit comments