title | titleSuffix | description | services | ms.service | ms.subservice | ms.custom | ms.topic | ms.author | author | ms.date |
---|---|---|---|---|---|---|---|---|---|---|
CLI (v2) release notes |
Azure Machine Learning |
Learn about the latest updates to Azure Machine Learning CLI (v2) |
machine-learning |
machine-learning |
core |
event-tier1-build-2022 |
reference |
larryfr |
blackmist |
04/12/2022 |
[!INCLUDE cli v2]
In this article, learn about Azure Machine Learning CLI (v2) releases.
RSS feed: Get notified when this page is updated by copying and pasting the following URL into your feed reader:
https://docs.microsoft.com/api/search/rss?search=%22Azure+machine+learning+release+notes-v2%22&locale=en-us
- The Azure Machine Learning CLI (v2) is now GA.
az ml job
- The command group is marked as GA.
- Added AutoML job type in public preview.
- Added
schedules
property to pipeline job in public preview. - Added an option to list only archived jobs.
- Improved reliability of
az ml job download
command.
az ml data
- The command group is marked as GA.
- Added MLTable data type in public preview.
- Added an option to list only archived data assets.
az ml environment
- Added an option to list only archived environments.
az ml model
- The command group is marked as GA.
- Allow models to be created from job outputs.
- Added an option to list only archived models.
az ml online-deployment
- The command group is marked as GA.
- Removed timeout waiting for deployment creation.
- Improved online deployment list view.
az ml online-endpoint
- The command group is marked as GA.
- Added
mirror_traffic
property to online endpoints in public preview. - Improved online endpoint list view.
az ml batch-deployment
- The command group is marked as GA.
- Added support for
uri_file
anduri_folder
as invocation input. - Fixed a bug in batch deployment update.
- Fixed a bug in batch deployment list-jobs output.
az ml batch-endpoint
- The command group is marked as GA.
- Added support for
uri_file
anduri_folder
as invocation input. - Fixed a bug in batch endpoint update.
- Fixed a bug in batch endpoint list-jobs output.
az ml component
- The command group is marked as GA.
- Added an option to list only archived components.
az ml code
- This command group is removed.
az ml job
- For all job types, flattened the
code
section of the YAML schema. Instead ofcode.local_path
to specify the path to the source code directory, it is now justcode
- For all job types, changed the schema for defining data inputs to the job in the job YAML. Instead of specifying the data path using either the
file
orfolder
fields, use thepath
field to specify either a local path, a URI to a cloud path containing the data, or a reference to an existing registered Azure ML data asset viapath: azureml:<data_name>:<data_version>
. Also specify thetype
field to clarify whether the data source is a single file (uri_file
) or a folder (uri_folder
). Iftype
field is omitted, it defaults totype: uri_folder
. For more information, see the section of any of the job YAML references that discuss the schema for specifying input data. - In the sweep job YAML schema, changed the
sampling_algorithm
field from a string to an object in order to support additional configurations for the random sampling algorithm type - Removed the component job YAML schema. With this release, if you want to run a command job inside a pipeline that uses a component, just specify the component to the
component
field of the command job YAML definition. - For all job types, added support for referencing the latest version of a nested asset in the job YAML configuration. When referencing a registered environment or data asset to use as input in a job, you can alias by latest version rather than having to explicitly specify the version. For example:
environment: azureml:AzureML-Minimal@latest
- For pipeline jobs, introduced the
${{ parent }}
context for binding inputs and outputs between steps in a pipeline. For more information, see Expression syntax for binding inputs and outputs between steps in a pipeline job. - Added support for downloading named outputs of job via the
--output-name
argument for theaz ml job download
command
- For all job types, flattened the
az ml data
- Deprecated the
az ml dataset
subgroup, now usingaz ml data
instead - There are two types of data that can now be created, either from a single file source (
type: uri_file
) or a folder (type: uri_folder
). When creating the data asset, you can either specify the data source from a local file / folder or from a URI to a cloud path location. See the data YAML schema for the full schema
- Deprecated the
az ml environment
- In the environment YAML schema, renamed the
build.local_path
field tobuild.path
- Removed the
build.context_uri
field, the URI of the uploaded build context location will be accessible viabuild.path
when the environment is returned
- In the environment YAML schema, renamed the
az ml model
- In the model YAML schema,
model_uri
andlocal_path
fields removed and consolidated to onepath
field that can take either a local path or a cloud path URI.model_format
field renamed totype
; the default type iscustom_model
, but you can specify one of the other types (mlflow_model
,triton_model
) to use the model in no-code deployment scenarios - For
az ml model create
,--model-uri
and--local-path
arguments removed and consolidated to one--path
argument that can take either a local path or a cloud path URI - Added the
az ml model download
command to download a model's artifact files
- In the model YAML schema,
az ml online-deployment
- In the online deployment YAML schema, flattened the
code
section of thecode_configuration
field. Instead ofcode_configuration.code.local_path
to specify the path to the source code directory containing the scoring files, it is now justcode_configuration.code
- Added an
environment_variables
field to the online deployment YAML schema to support configuring environment variables for an online deployment
- In the online deployment YAML schema, flattened the
az ml batch-deployment
- In the batch deployment YAML schema, flattened the
code
section of thecode_configuration
field. Instead ofcode_configuration.code.local_path
to specify the path to the source code directory containing the scoring files, it is now justcode_configuration.code
- In the batch deployment YAML schema, flattened the
az ml component
- Flattened the
code
section of the command component YAML schema. Instead ofcode.local_path
to specify the path to the source code directory, it is now justcode
- Added support for referencing the latest version of a registered environment to use in the component YAML configuration. When referencing a registered environment, you can alias by latest version rather than having to explicitly specify the version. For example:
environment: azureml:AzureML-Minimal@latest
- Renamed the component input and output type value from
path
touri_folder
for thetype
field when defining a component input or output
- Flattened the
- Removed the
delete
commands for assets (model, component, data, environment). The existing delete functionality is only a soft delete, so thedelete
commands will be reintroduced in a later release once hard delete is supported - Added support for archiving and restoring assets (model, component, data, environment) and jobs, e.g.
az ml model archive
andaz ml model restore
. You can now archive assets and jobs, which will hide the archived entity from list queries (e.g.az ml model list
).
az ml workspace
- Updated workspace YAML schema
az ml compute
- Updated YAML schemas for AmlCompute and Compute Instance
- Removed support for legacy AKS attach via
az ml compute attach
. Azure Arc-enabled Kubernetes attach will be supported in the next release
az ml datastore
- Updated YAML schemas for Azure blob, Azure file, Azure Data Lake Gen1, and Azure Data Lake Gen2 datastores
- Added support for creating Azure Data Lake Storage Gen1 and Gen2 datastores
az ml job
- Updated YAML schemas for command job and sweep job
- Added support for running pipeline jobs (pipeline job YAML schema)
- Added support for job input literals and input data URIs for all job types
- Added support for job outputs for all job types
- Changed the expression syntax from
{ <expression> }
to${{ <expression> }}
. For more information, see Expression syntax for configuring Azure ML jobs
az ml environment
- Updated environment YAML schema
- Added support for creating environments from Docker build context
az ml model
- Updated model YAML schema
- Added new
model_format
property to Model for no-code deployment scenarios
az ml dataset
- Renamed
az ml data
subgroup toaz ml dataset
- Updated dataset YAML schema
- Renamed
az ml component
- Added the
az ml component
commands for managing Azure ML components - Added support for command components (command component YAML schema)
- Added the
az ml online-endpoint
az ml endpoint
subgroup split into two separate groups:az ml online-endpoint
andaz ml batch-endpoint
- Updated online endpoint YAML schema
- Added support for local endpoints for dev/test scenarios
- Added interactive VSCode debugging support for local endpoints (added the
--vscode-debug
flag toaz ml batch-endpoint create/update
)
az ml online-deployment
az ml deployment
subgroup split into two separate groups:az ml online-deployment
andaz ml batch-deployment
- Updated managed online deployment YAML schema
- Added autoscaling support via integration with Azure Monitor Autoscale
- Added support for updating multiple online deployment properties in the same update operation
- Added support for performing concurrent operations on deployments under the same endpoint
az ml batch-endpoint
az ml endpoint
subgroup split into two separate groups:az ml online-endpoint
andaz ml batch-endpoint
- Updated batch endpoint YAML schema
- Removed
traffic
property; replaced with a configurable default deployment property - Added support for input data URIs for
az ml batch-endpoint invoke
- Added support for VNet ingress (private link)
az ml batch-deployment
az ml deployment
subgroup split into two separate groups:az ml online-deployment
andaz ml batch-deployment
- Updated batch deployment YAML schema
The ml
extension to the Azure CLI is the next-generation interface for Azure Machine Learning. It enables you to train and deploy models from the command line, with features that accelerate scaling data science up and out while tracking the model lifecycle. Install and get started.