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
@@ -48,6 +48,7 @@ The source JSON schema can be found at https://azuremlschemas.azureedge.net/late
48
48
|`inputs.<input_name>`| number, integer, boolean, string or object | One of a literal value (of type number, integer, boolean, or string) or an object containing a [job input data specification](#job-inputs). |||
49
49
|`outputs`| object | Dictionary of output configurations of the job. The key is a name for the output within the context of the job and the value is the output configuration. <br><br> Outputs can be referenced in the `command` using the `${{ outputs.<output_name> }}` expression. ||
50
50
|`outputs.<output_name>`| object | You can leave the object empty, in which case by default the output will be of type `uri_folder` and Azure ML will system-generate an output location for the output. File(s) to the output directory will be written via read-write mount. If you want to specify a different mode for the output, provide an object containing the [job output specification](#job-outputs). ||
51
+
|`identity`| object | The identity is used for data accessing. It can be [UserIdentityConfiguration](#useridentityconfiguration), [ManagedIdentityConfiguration](#managedidentityconfiguration) or None. If it's UserIdentityConfiguration the identity of job submitter will be used to access input data and write result to output folder, otherwise, the managed identity of the compute target will be used ||
51
52
52
53
### Distribution configurations
53
54
@@ -88,6 +89,16 @@ The source JSON schema can be found at https://azuremlschemas.azureedge.net/late
88
89
|`type`| string | The type of job output. For the default `uri_folder` type, the output will correspond to a folder. |`uri_folder` , `mlflow_model`, `custom_model`|`uri_folder`|
89
90
|`mode`| string | Mode of how output file(s) will get delivered to the destination storage. For read-write mount mode (`rw_mount`) the output directory will be a mounted directory. For upload mode the file(s) written will get uploaded at the end of the job. |`rw_mount`, `upload`|`rw_mount`|
Copy file name to clipboardExpand all lines: articles/machine-learning/reference-yaml-job-pipeline.md
+12-1Lines changed: 12 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ ms.topic: reference
9
9
ms.custom: cliv2, event-tier1-build-2022
10
10
author: cloga
11
11
ms.author: lochen
12
-
ms.date: 08/08/2022
12
+
ms.date: 11/28/2022
13
13
ms.reviewer: scottpolly
14
14
---
15
15
@@ -42,6 +42,7 @@ The source JSON schema can be found at https://azuremlschemas.azureedge.net/late
42
42
|`inputs.<input_name>`| number, integer, boolean, string or object | One of a literal value (of type number, integer, boolean, or string) or an object containing a [job input data specification](#job-inputs). |||
43
43
|`outputs`| object | Dictionary of output configurations of the pipeline job. The key is a name for the output within the context of the job and the value is the output configuration. <br><br> These pipeline outputs can be referenced by the outputs of an individual step job in the pipeline using the `${{ parents.outputs.<output_name> }}` expression. For more information on how to bind the inputs of a pipeline step to the inputs of the top-level pipeline job, see the [Expression syntax for binding inputs and outputs between steps in a pipeline job](reference-yaml-core-syntax.md#binding-inputs-and-outputs-between-steps-in-a-pipeline-job). ||
44
44
|`outputs.<output_name>`| object | You can leave the object empty, in which case by default the output will be of type `uri_folder` and Azure ML will system-generate an output location for the output based on the following templatized path: `{settings.datastore}/azureml/{job-name}/{output-name}/`. File(s) to the output directory will be written via read-write mount. If you want to specify a different mode for the output, provide an object containing the [job output specification](#job-outputs). ||
45
+
|`identity`| object | The identity is used for data accessing. It can be [UserIdentityConfiguration](#useridentityconfiguration), [ManagedIdentityConfiguration](#managedidentityconfiguration) or None. If it's UserIdentityConfiguration the identity of job submitter will be used to access input data and write result to output folder, otherwise, the managed identity of the compute target will be used ||
45
46
46
47
### Attributes of the `settings` key
47
48
@@ -66,6 +67,16 @@ The source JSON schema can be found at https://azuremlschemas.azureedge.net/late
66
67
|`type`| string | The type of job output. For the default `uri_folder` type, the output will correspond to a folder. |`uri_file`, `uri_folder`, `mltable`, `mlflow_model`|`uri_folder`|
67
68
|`mode`| string | Mode of how output file(s) will get delivered to the destination storage. For read-write mount mode (`rw_mount`) the output directory will be a mounted directory. For upload mode the file(s) written will get uploaded at the end of the job. |`rw_mount`, `upload`|`rw_mount`|
Copy file name to clipboardExpand all lines: articles/machine-learning/reference-yaml-job-sweep.md
+13-2Lines changed: 13 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,8 +9,8 @@ ms.topic: reference
9
9
ms.custom: cliv2, event-tier1-build-2022
10
10
ms.author: amipatel
11
11
author: amibp
12
-
ms.date: 08/08/2022
13
-
ms.reviewer: nibaccam
12
+
ms.date: 11/28/2022
13
+
ms.reviewer: larryfr
14
14
---
15
15
16
16
# CLI (v2) sweep job YAML schema
@@ -47,6 +47,7 @@ The source JSON schema can be found at https://azuremlschemas.azureedge.net/late
47
47
|`inputs.<input_name>`| number, integer, boolean, string or object | One of a literal value (of type number, integer, boolean, or string) or an object containing a [job input data specification](#job-inputs). |||
48
48
|`outputs`| object | Dictionary of output configurations of the job. The key is a name for the output within the context of the job and the value is the output configuration. <br><br> Outputs can be referenced in the `command` using the `${{ outputs.<output_name> }}` expression. ||
49
49
|`outputs.<output_name>`| object | You can leave the object empty, in which case by default the output will be of type `uri_folder` and Azure ML will system-generate an output location for the output. File(s) to the output directory will be written via read-write mount. If you want to specify a different mode for the output, provide an object containing the [job output specification](#job-outputs). ||
50
+
|`identity`| object | The identity is used for data accessing. It can be [UserIdentityConfiguration](#useridentityconfiguration), [ManagedIdentityConfiguration](#managedidentityconfiguration) or None. If it's UserIdentityConfiguration the identity of job submitter will be used to access input data and write result to output folder, otherwise, the managed identity of the compute target will be used ||
50
51
51
52
### Sampling algorithms
52
53
@@ -216,6 +217,16 @@ The source JSON schema can be found at https://azuremlschemas.azureedge.net/late
216
217
|`type`| string | The type of job output. For the default `uri_folder` type, the output will correspond to a folder. |`uri_file`, `uri_folder`, `mltable`, `mlflow_model`|`uri_folder`|
217
218
|`mode`| string | Mode of how output file(s) will get delivered to the destination storage. For read-write mount mode (`rw_mount`) the output directory will be a mounted directory. For upload mode the file(s) written will get uploaded at the end of the job. |`rw_mount`, `upload`|`rw_mount`|
0 commit comments