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
Copy file name to clipboardExpand all lines: articles/data-factory/author-visually.md
+27-27Lines changed: 27 additions & 27 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,18 +12,18 @@ ms.workload: data-services
12
12
ms.tgt_pltfrm: na
13
13
ms.devlang: na
14
14
ms.topic: conceptual
15
-
ms.date: 09/18/2018
15
+
ms.date: 09/19/2018
16
16
ms.author: shlo
17
17
18
18
---
19
19
# Visual authoring in Azure Data Factory
20
20
The Azure Data Factory user interface experience (UX) lets you visually author and deploy resources for your data factory without having to write any code. You can drag activities to a pipeline canvas, perform test runs, debug iteratively, and deploy and monitor your pipeline runs. There are two approaches for using the UX to perform visual authoring:
21
21
22
22
- Author directly with the Data Factory service.
23
-
- Author with Azure DevOps Git integration for collaboration, source control, or versioning.
23
+
- Author with Git integration with Azure Repos for collaboration, source control, or versioning.
24
24
25
25
## Author directly with the Data Factory service
26
-
Visual authoring with the Data Factory service differs from visual authoring with Azure DevOps in two ways:
26
+
Visual authoring with the Data Factory service differs from visual authoring with Azure DevOps Services in two ways:
27
27
28
28
- The Data Factory service doesn't include a repository for storing the JSON entities for your changes.
29
29
- The Data Factory service isn't optimized for collaboration or version control.
@@ -34,39 +34,39 @@ When you use the UX **Authoring canvas** to author directly with the Data Factor
Visual authoring with Azure DevOps Git integration supports source control and collaboration for work on your data factory pipelines. You can associate a data factory with an Azure DevOps Git organization repository for source control, collaboration, versioning, and so on. A single Azure DevOps Git organization can have multiple repositories, but an Azure DevOps Git repository can be associated with only one data factory. If you don't have an Azure DevOps organization or repository, follow [these instructions](https://docs.microsoft.com/azure/devops/organizations/accounts/create-organization-msa-or-work-student) to create your resources.
37
+
## Author with Git integration with Azure Repos
38
+
Visual authoring with Git integration with Azure Repos supports source control and collaboration for work on your data factory pipelines. You can associate a data factory with an Azure Repos Git organization repository for source control, collaboration, versioning, and so on. A single Azure Repos Git organization can have multiple repositories, but an Azure Repos Git repository can be associated with only one data factory. If you don't have an Azure Repos organization or repository, follow [these instructions](https://docs.microsoft.com/azure/devops/organizations/accounts/create-organization-msa-or-work-student) to create your resources.
39
39
40
40
> [!NOTE]
41
-
> You can store script and data files in an Azure DevOps Git repository. However, you have to upload the files manually to Azure Storage. A Data Factory pipeline does not automatically upload script or data files stored in an Azure DevOps Git repository to Azure Storage.
41
+
> You can store script and data files in an Azure Repos Git repository. However, you have to upload the files manually to Azure Storage. A Data Factory pipeline does not automatically upload script or data files stored in an Azure Repos Git repository to Azure Storage.
42
42
43
-
### Configure an Azure DevOps Git repository with Azure Data Factory
44
-
You can configure an Azure DevOps Git repository with a data factory through two methods.
43
+
### Configure an Azure Repos Git repository with Azure Data Factory
44
+
You can configure an Azure Repos Git repository with a data factory through two methods.
45
45
46
-
#### <aname="method1"></a> Configuration method 1 (Azure DevOps Git repo): Let's get started page
46
+
#### <aname="method1"></a> Configuration method 1 (Azure Repos Git repo): Let's get started page
47
47
48
48
In Azure Data Factory, go to the **Let's get started** page. Select **Configure Code Repository**:
49
49
50
-
50
+
51
51
52
52
The **Repository Settings** configuration pane appears:
53
53
54
54
55
55
56
-
The pane shows the following Azure DevOps code repository settings:
56
+
The pane shows the following Azure Repos code repository settings:
57
57
58
58
| Setting | Description | Value |
59
59
|:--- |:--- |:--- |
60
-
|**Repository Type**| The type of the Azure DevOps code repository.<br/>**Note**: GitHub is not currently supported. | Azure Dev Ops Git |
60
+
|**Repository Type**| The type of the Azure Repos code repository.<br/>**Note**: GitHub is not currently supported. | Azure Dev Ops Git |
61
61
|**Azure Active Directory**| Your Azure AD tenant name. | <yourtenantname> |
62
-
|**Azure DevOps Organization**| Your Azure DevOps organization name. You can locate your Azure DevOps organization name at `https://{organization name}.visualstudio.com`. You can [sign in to your Azure DevOps organization](https://www.visualstudio.com/team-services/git/) to access your Visual Studio profile and see your repositories and projects. | <yourorganizationname> |
63
-
|**ProjectName**| Your Azure DevOps project name. You can locate your Azure DevOps project name at `https://{organization name}.visualstudio.com/{project name}`. | <yourAzureDevOpsprojectname> |
64
-
|**RepositoryName**| Your Azure DevOps code repository name. Azure DevOps projects contain Git repositories to manage your source code as your project grows. You can create a new repository or use an existing repository that's already in your project. | <yourAzureDevOpscoderepositoryname> |
65
-
|**Collaboration branch**| Your Azure DevOps collaboration branch that is used for publishing. By default, it is `master`. Change this setting in case you want to publish resources from another branch. | <yourcollaborationbranchname> |
66
-
|**Root folder**| Your root folder in your Azure DevOps collaboration branch. | <yourrootfoldername> |
67
-
|**Import existing Data Factory resources to repository**| Specifies whether to import existing data factory resources from the UX **Authoring canvas** into an Azure DevOps Git repository. Select the box to import your data factory resources into the associated Git repository in JSON format. This action exports each resource individually (that is, the linked services and datasets are exported into separate JSONs). When this box isn't selected, the existing resources aren't imported. | Selected (default) |
|**Azure Repos Organization**| Your Azure Repos organization name. You can locate your Azure Repos organization name at `https://{organization name}.visualstudio.com`. You can [sign in to your Azure Repos organization](https://www.visualstudio.com/team-services/git/) to access your Visual Studio profile and see your repositories and projects. | <yourorganizationname> |
63
+
|**ProjectName**| Your Azure Repos project name. You can locate your Azure Repos project name at `https://{organization name}.visualstudio.com/{project name}`. | <yourAzureReposprojectname> |
64
+
|**RepositoryName**| Your Azure Repos code repository name. Azure Repos projects contain Git repositories to manage your source code as your project grows. You can create a new repository or use an existing repository that's already in your project. | <yourAzureReposcoderepositoryname> |
65
+
|**Collaboration branch**| Your Azure Repos collaboration branch that is used for publishing. By default, it is `master`. Change this setting in case you want to publish resources from another branch. | <yourcollaborationbranchname> |
66
+
|**Root folder**| Your root folder in your Azure Repos collaboration branch. | <yourrootfoldername> |
67
+
|**Import existing Data Factory resources to repository**| Specifies whether to import existing data factory resources from the UX **Authoring canvas** into an Azure Repos Git repository. Select the box to import your data factory resources into the associated Git repository in JSON format. This action exports each resource individually (that is, the linked services and datasets are exported into separate JSONs). When this box isn't selected, the existing resources aren't imported. | Selected (default) |
In the Azure Data Factory UX **Authoring canvas**, locate your data factory. Select the **Data Factory** drop-down menu, and then select **Configure Code Repository**.
71
71
72
72
A configuration pane appears. For details about the configuration settings, see the descriptions in <ahref="#method1">Configuration method 1</a>.
@@ -75,7 +75,7 @@ A configuration pane appears. For details about the configuration settings, see
75
75
76
76
## Use a different Azure Active Directory tenant
77
77
78
-
You can create an Azure DevOps Git repo in a different Azure Active Directory tenant. To specify a different Azure AD tenant, you have to have administrator permissions for the Azure subscription that you're using.
78
+
You can create an Azure Repos Git repo in a different Azure Active Directory tenant. To specify a different Azure AD tenant, you have to have administrator permissions for the Azure subscription that you're using.
79
79
80
80
## Switch to a different Git repo
81
81
@@ -88,11 +88,11 @@ After you remove the association with the current repo, you can configure your G
88
88
## Use version control
89
89
Version control systems (also known as _source control_) let developers collaborate on code and track changes that are made to the code base. Source control is an essential tool for multi-developer projects.
90
90
91
-
Each Azure DevOps Git repository that's associated with a data factory has a collaboration branch. (`master` is the default collaboration branch). Users can also create feature branches by clicking **+ New Branch** and do development in the feature branches.
91
+
Each Azure Repos Git repository that's associated with a data factory has a collaboration branch. (`master` is the default collaboration branch). Users can also create feature branches by clicking **+ New Branch** and do development in the feature branches.
92
92
93
93
94
94
95
-
When you are ready with the feature development in your feature branch, you can click **Create pull request**. This action takes you to Azure DevOps Git where you can raise pull requests, do code reviews, and merge changes to your collaboration branch. (`master` is the default). You are only allowed to publish to the Data Factory service from your collaboration branch.
95
+
When you are ready with the feature development in your feature branch, you can click **Create pull request**. This action takes you to Azure Repos Git where you can raise pull requests, do code reviews, and merge changes to your collaboration branch. (`master` is the default). You are only allowed to publish to the Data Factory service from your collaboration branch.
96
96
97
97
98
98
@@ -150,11 +150,11 @@ The **Repository Settings** configuration pane appears:
|**Repository Type**| The type of the Azure DevOps code repository. | GitHub |
157
+
|**Repository Type**| The type of the Azure Repos code repository. | GitHub |
158
158
|**GitHub account**| Your GitHub account name. This name can be found from https://github.com/{account name}/{repository name}. Navigating to this page prompts you to enter GitHub OAuth credentials to your GitHub account. ||
159
159
|**RepositoryName**| Your GitHub code repository name. GitHub accounts contain Git repositories to manage your source code. You can create a new repository or use an existing repository that's already in your account. ||
160
160
|**Collaboration branch**| Your GitHub collaboration branch that is used for publishing. By default, it is master. Change this setting in case you want to publish resources from another branch. ||
@@ -182,11 +182,11 @@ The **Repository Settings** configuration pane appears:
|**Repository Type**| The type of the Azure DevOps code repository. | GitHub |
189
+
|**Repository Type**| The type of the Azure Repos code repository. | GitHub |
190
190
|**Use GitHub Enterprise**| Checkbox to select GitHub Enterprise ||
191
191
|**GitHub Enterprise URL**| The GitHub Enterprise root URL. For example: https://github.mydomain.com||
192
192
|**GitHub account**| Your GitHub account name. This name can be found from https://github.com/{account name}/{repository name}. Navigating to this page prompts you to enter GitHub OAuth credentials to your GitHub account. ||
0 commit comments