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/concepts-pipeline-execution-triggers.md
+22-15Lines changed: 22 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -37,7 +37,7 @@ You will see the trigger configuration window, allowing you to choose the trigge
37
37
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.
38
38
39
39
40
-
## Manual execution (on-demand) with JSON
40
+
## Manual execution with JSON
41
41
42
42
The manual execution of a pipeline is also referred to as _on-demand_ execution.
43
43
@@ -87,22 +87,27 @@ For example, say you have a basic pipeline named **copyPipeline** that you want
87
87
88
88
In the JSON definition, the pipeline takes two parameters: **sourceBlobContainer** and **sinkBlobContainer**. You pass values to these parameters at runtime.
89
89
90
+
## Manual execution with other APIs/SDKs
91
+
90
92
You can manually run your pipeline by using one of the following methods:
93
+
91
94
- .NET SDK
92
95
- Azure PowerShell module
93
96
- REST API
94
97
- Python SDK
95
98
96
-
### REST API
99
+
### .NET SDK
97
100
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:
0 commit comments