Skip to content

Commit 94aaec4

Browse files
authored
Update concepts-pipeline-execution-triggers.md
1 parent 30ed86f commit 94aaec4

File tree

1 file changed

+22
-15
lines changed

1 file changed

+22
-15
lines changed

articles/data-factory/concepts-pipeline-execution-triggers.md

Lines changed: 22 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ You will see the trigger configuration window, allowing you to choose the trigge
3737
Read more about [scheduled](#schedule-trigger-with-json), [tumbling window](#tumbling-window-trigger), [storage event](#event-based-trigger), and [custom event](#event-based-trigger) triggers below.
3838

3939

40-
## Manual execution (on-demand) with JSON
40+
## Manual execution with JSON
4141

4242
The manual execution of a pipeline is also referred to as _on-demand_ execution.
4343

@@ -87,22 +87,27 @@ For example, say you have a basic pipeline named **copyPipeline** that you want
8787

8888
In the JSON definition, the pipeline takes two parameters: **sourceBlobContainer** and **sinkBlobContainer**. You pass values to these parameters at runtime.
8989

90+
## Manual execution with other APIs/SDKs
91+
9092
You can manually run your pipeline by using one of the following methods:
93+
9194
- .NET SDK
9295
- Azure PowerShell module
9396
- REST API
9497
- Python SDK
9598

96-
### REST API
99+
### .NET SDK
97100

98-
The following sample command shows you how to run your pipeline by using the REST API manually:
101+
The following sample call shows you how to run your pipeline by using the .NET SDK manually:
99102

100-
```
101-
POST
102-
https://management.azure.com/subscriptions/mySubId/resourceGroups/myResourceGroup/providers/Microsoft.DataFactory/factories/myDataFactory/pipelines/copyPipeline/createRun?api-version=2017-03-01-preview
103+
```csharp
104+
client.Pipelines.CreateRunWithHttpMessagesAsync(resourceGroup, dataFactoryName, pipelineName, parameters)
103105
```
104106

105-
For a complete sample, see [Quickstart: Create a data factory by using the REST API](quickstart-create-data-factory-rest-api.md).
107+
For a complete sample, see [Quickstart: Create a data factory by using the .NET SDK](quickstart-create-data-factory-dot-net.md).
108+
109+
> [!NOTE]
110+
> You can use the .NET SDK to invoke pipelines from Azure Functions, from your web services, and so on.
106111
107112
### Azure PowerShell
108113

@@ -133,18 +138,20 @@ The response payload is a unique ID of the pipeline run:
133138

134139
For a complete sample, see [Quickstart: Create a data factory by using Azure PowerShell](quickstart-create-data-factory-powershell.md).
135140

136-
### .NET SDK
141+
### Python SDK
137142

138-
The following sample call shows you how to run your pipeline by using the .NET SDK manually:
143+
For a complete sample, see [Quickstart: Create a data factory and pipeline using Python](quickstart-create-data-factory-python.md)
139144

140-
```csharp
141-
client.Pipelines.CreateRunWithHttpMessagesAsync(resourceGroup, dataFactoryName, pipelineName, parameters)
142-
```
145+
### REST API
143146

144-
For a complete sample, see [Quickstart: Create a data factory by using the .NET SDK](quickstart-create-data-factory-dot-net.md).
147+
The following sample command shows you how to run your pipeline by using the REST API manually:
145148

146-
> [!NOTE]
147-
> You can use the .NET SDK to invoke pipelines from Azure Functions, from your web services, and so on.
149+
```
150+
POST
151+
https://management.azure.com/subscriptions/mySubId/resourceGroups/myResourceGroup/providers/Microsoft.DataFactory/factories/myDataFactory/pipelines/copyPipeline/createRun?api-version=2017-03-01-preview
152+
```
153+
154+
For a complete sample, see [Quickstart: Create a data factory by using the REST API](quickstart-create-data-factory-rest-api.md).
148155

149156
## Trigger execution with JSON
150157

0 commit comments

Comments
 (0)