Skip to content

Commit f092b57

Browse files
committed
one try
1 parent 3f59506 commit f092b57

File tree

2 files changed

+3
-1
lines changed

2 files changed

+3
-1
lines changed

articles/machine-learning/how-to-manage-inputs-outputs-pipeline.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -234,6 +234,7 @@ The following code example shows how to define optional input. When the input is
234234
In a pipeline graph, optional inputs of data/model types are represented by dotted circles. Optional inputs of primitive types are in the **Settings** tab. Unlike required inputs, optional inputs don't have an asterisk next to them, indicating that they aren't mandatory.
235235

236236
:::image type="content" source="./media/how-to-manage-pipeline-input-output/optional-input.png" lightbox="./media/how-to-manage-pipeline-input-output/optional-input.png" alt-text="Screenshot highlighting the optional input.":::
237+
237238
---
238239

239240
## Customize output paths
@@ -277,9 +278,10 @@ You can download outputs at the pipeline or component level.
277278

278279
### Download pipeline-level outputs
279280

281+
# [Azure CLI](#tab/cli)
282+
280283
You can download all the outputs of a job or download a specific output.
281284

282-
# [Azure CLI](#tab/cli)
283285
```azurecli
284286
# Download all the outputs of the job
285287
az ml job download --all -n <JOB_NAME> -g <RESOURCE_GROUP_NAME> -w <WORKSPACE_NAME> --subscription <SUBSCRIPTION_ID>

0 commit comments

Comments
 (0)