Skip to content

Commit 41d3e5d

Browse files
committed
Fixes
1 parent 2c71987 commit 41d3e5d

File tree

1 file changed

+13
-18
lines changed

1 file changed

+13
-18
lines changed

articles/data-factory/continuous-integration-delivery-automate-azure-pipelines.md

Lines changed: 13 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -47,35 +47,30 @@ The following is a guide for setting up an Azure Pipelines release that automate
4747

4848
1. Add an Azure Resource Manager Deployment task:
4949

50-
a. In the stage view, select **View stage tasks**.
50+
1. In the stage view, select **View stage tasks**.
5151

52-
:::image type="content" source="media/continuous-integration-delivery/continuous-integration-image14.png" alt-text="Stage view":::
52+
:::image type="content" source="media/continuous-integration-delivery/continuous-integration-image14.png" alt-text="Stage view":::
5353

54-
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**.
5555

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.
5757

58-
d. In the **Action** list, select **Create or update resource group**.
58+
1. In the **Action** list, select **Create or update resource group**.
5959

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).
6161

62-
# MS CSS got many support cases that except the maximum size limitation of ARM template
63-
# so please consider too add some docs here
64-
https://learn.microsoft.com/en-us/azure/data-factory/continuous-integration-delivery-linked-templates#using-linked-templates
65-
https://learn.microsoft.com/en-us/archive/blogs/najib/deploying-linked-arm-templates-with-vsts
62+
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.
6663

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.
6865

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**.
7067

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)
7270
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)
71+
:::image type="content" source="media/continuous-integration-delivery/continuous-integration-image9.png" alt-text="Data Factory Prod Deployment":::
7572

76-
:::image type="content" source="media/continuous-integration-delivery/continuous-integration-image9.png" alt-text="Data Factory Prod Deployment":::
77-
78-
1. Save the release pipeline.
73+
1. Save the release pipeline.
7974

8075
1. To trigger a release, select **Create release**. To automate the creation of releases, see [Azure DevOps release triggers](/azure/devops/pipelines/release/triggers)
8176

0 commit comments

Comments
 (0)