text:
Add async methods to CosmosSerializer

Is your feature request related to a problem? Please describe.
Currently CosmosSerializer only has synchronous methods.
In order to create a custom serializer that uses the new JsonSerializer in .NET Core 3, async methods should be added to CosmosSerializer. The default implementation can just call the synchronous methods to support backwards compatibility.
Describe the solution you'd like
//------------------------------------------------------------
// Copyright (c) Microsoft Corporation.  All rights reserved.
//------------------------------------------------------------

namespace Microsoft.Azure.Cosmos
{
    using System;
    using System.IO;
    using System.Threading;
    using System.Threading.Tasks;

    /// <summary>
    /// This is an interface to allow a custom serializer to be used by the CosmosClient
    /// </summary>
    public abstract class CosmosSerializer
    {
        /// <summary>
        /// Convert a Stream of JSON to an object.
        /// The caller will ensure the stream is disposed.
        /// This will prevent memory leaks if an exception is hit.
        /// </summary>
        /// <typeparam name="T">Any typed passed to <see cref="Container"/></typeparam>
        /// <param name="stream">The Stream response containing JSON from Cosmos</param>
        /// <returns>The object deserialized from the stream.</returns>
        public abstract T FromStream<T>(Stream stream);

        /// <summary>
        /// Convert the object to a Stream.
        /// The caller will take ownership of the stream and ensure it is correctly disposed of.
        /// Stream.CanRead must be true https://docs.microsoft.com/dotnet/api/system.io.stream.canread?view=netcore-2.0
        /// </summary>
        /// <param name="input">Any typed passed to <see cref="Container"/></param>
        /// <returns>A readable Stream containing JSON of the serialized object</returns>
        public abstract Stream ToStream<T>(T input);

        /// <summary>
        /// Convert a Stream of JSON to an object.
        /// The caller will ensure the stream is disposed.
        /// This will prevent memory leaks if an exception is hit.
        /// </summary>
        /// <typeparam name="T">Any typed passed to <see cref="Container"/></typeparam>
        /// <param name="stream">The Stream response containing JSON from Cosmos</param>
        /// <param name="cancellationToken"></param>
        /// <returns>The object deserialized from the stream.</returns>
        public virtual ValueTask<T> FromStreamAsync<T>(Stream stream, CancellationToken cancellationToken = default)
        {
            try
            {
                return new ValueTask<T>(this.FromStream<T>(stream));
            }
            catch (Exception ex)
            {
                return new ValueTask<T>(Task.FromException<T>(ex));
            }
        }

        /// <summary>
        /// Convert the object to a Stream.
        /// The caller will take ownership of the stream and ensure it is correctly disposed of.
        /// Stream.CanRead must be true https://docs.microsoft.com/dotnet/api/system.io.stream.canread?view=netcore-2.0
        /// </summary>
        /// <param name="input">Any typed passed to <see cref="Container"/></param>
        /// <param name="cancellationToken"></param>
        /// <returns>A readable Stream containing JSON of the serialized object</returns>
        public virtual ValueTask<Stream> ToStreamAsync<T>(T input, CancellationToken cancellationToken = default)
        {
            try
            {
                return new ValueTask<Stream>(this.ToStream(input));
            }
            catch (Exception ex)
            {
                return new ValueTask<Stream>(Task.FromException<Stream>(ex));
            }
        }
    }
}

+1 to this. I've just updated an application to use the v3 Cosmos SDK, and then subsequently run into this while updating the branch of the app using ASP.NET Core 3.0 preview 8.
In the meantime, I came up with this implementation that uses the synchronous APIs for System.Text.Json.
using System.IO;
using System.Text.Json;
using Microsoft.Azure.Cosmos;

namespace MyApp
{
    public class SystemTextJsonCosmosSerializer : CosmosSerializer
    {
        private readonly JsonSerializerOptions _options;

        public SystemTextJsonCosmosSerializer(JsonSerializerOptions options)
        {
            _options = options;
        }

        /// <inheritdoc />
        public override T FromStream<T>(Stream stream)
        {
            // Have to dispose of the stream, otherwise the Cosmos SDK throws.
            // https://github.com/Azure/azure-cosmos-dotnet-v3/blob/0843cae3c252dd49aa8e392623d7eaaed7eb712b/Microsoft.Azure.Cosmos/src/Serializer/CosmosJsonSerializerWrapper.cs#L22
            // https://github.com/Azure/azure-cosmos-dotnet-v3/blob/0843cae3c252dd49aa8e392623d7eaaed7eb712b/Microsoft.Azure.Cosmos/src/Serializer/CosmosJsonDotNetSerializer.cs#L73
            using (stream)
            {
                // TODO Would be more efficient if CosmosSerializer supported async
                using var memory = new MemoryStream((int)stream.Length);
                stream.CopyTo(memory);

                byte[] utf8Json = memory.ToArray();

                return JsonSerializer.Deserialize<T>(utf8Json, _options);
            }
        }

        /// <inheritdoc />
        public override Stream ToStream<T>(T input)
        {
            byte[] utf8Json = JsonSerializer.SerializeToUtf8Bytes(input, _options);
            return new MemoryStream(utf8Json);
        }
    }
}

Practically ToStream is compute bound. Are there scenarios where async/task overload will be useful?
FromStream is interesting. Serializer which can work with partial stream's (non-buffered fully) can leverage/exploit the async part. One such case might be array or list, which can yield partial results.
CosmosClient currently invokes FromStream once the steam is materialized fully. And non-async contract might suffice.
@martincostello / @LeroyK please share the scenarios or data-sets which can leverage async contracts and Cosmos team is happy to explore them.

Closing the issue for now.
Please feel free to re-open with more context.

@kirankumarkolli The copy is used to do a simple synchronous copy of the bytes from the stream to an array to pass to the synchronous JsonSerializer deserialize method as a ReadOnlySpan<byte>. Stream is only accepted by the async methods.
The assumption here is that the streams hadn't been fully read by the caller, so would provide benefits from async usage. If the SDK consumes them all, then I guess the benefits would be minimal unless the SDK didn't eagerly consume the response stream before deserializing.

+1 to this. I've just updated an application to use the v3 Cosmos SDK, and then subsequently run into this while updating the branch of the app using ASP.NET Core 3.0 preview 8.
In the meantime, I came up with this implementation that uses the synchronous APIs for System.Text.Json.
using System.IO;
using System.Text.Json;
using Microsoft.Azure.Cosmos;

namespace MyApp
{
    public class SystemTextJsonCosmosSerializer : CosmosSerializer
    {
        private readonly JsonSerializerOptions _options;

        public SystemTextJsonCosmosSerializer(JsonSerializerOptions options)
        {
            _options = options;
        }

        /// <inheritdoc />
        public override T FromStream<T>(Stream stream)
        {
            // Have to dispose of the stream, otherwise the Cosmos SDK throws.
            // https://github.com/Azure/azure-cosmos-dotnet-v3/blob/0843cae3c252dd49aa8e392623d7eaaed7eb712b/Microsoft.Azure.Cosmos/src/Serializer/CosmosJsonSerializerWrapper.cs#L22
            // https://github.com/Azure/azure-cosmos-dotnet-v3/blob/0843cae3c252dd49aa8e392623d7eaaed7eb712b/Microsoft.Azure.Cosmos/src/Serializer/CosmosJsonDotNetSerializer.cs#L73
            using (stream)
            {
                // TODO Would be more efficient if CosmosSerializer supported async
                using var memory = new MemoryStream((int)stream.Length);
                stream.CopyTo(memory);

                byte[] utf8Json = memory.ToArray();

                return JsonSerializer.Deserialize<T>(utf8Json, _options);
            }
        }

        /// <inheritdoc />
        public override Stream ToStream<T>(T input)
        {
            byte[] utf8Json = JsonSerializer.SerializeToUtf8Bytes(input, _options);
            return new MemoryStream(utf8Json);
        }
    }
}

@martincostello when I use your implementation:
var client = new CosmosClientBuilder
		(accountEndpoint: "https://localhost:8081", "<key>")
		.WithCustomSerializer(new SystemTextJsonCosmosSerializer(new JsonSerializerOptions {}))
				.Build();

The spatial data type Point is not properly serialized.
	public Point Location { get; set; }

It should be serialized as with the Cosmos NET v3 SDK(Json,net) and v4 preview(System.Text.Json) as:
   "location": {
        "type": "Point",
        "coordinates": [
            8.000,
            47.000
        ]
    },

But instead it ends up like this:
   "location": {
        "Position": {
            "Coordinates": [
                8.0000,
                47.0000
            ],
            "Longitude": 8.0000,
            "Latitude": 47.0000,
            "Altitude": null
        },
        "Crs": {
            "Type": 0
        },
        "Type": 0,
        "BoundingBox": null,
        "AdditionalProperties": {}
    },

Do you have any idea why?

I guess that it has a custom serialiser somewhere, so System.Text.Json is just serialising the literal object layout. If that’s the case you’d have to create a custom serialiser for the Point type and register it with your JsonSerializerSettings instance.

Hi team, we use CosmosSerializer for our migration process. As part of our migration, we deserialize the JSON document from Cosmos as JObject and then update the JObject as per the latest schema of the Document. The advantage of this approach for us is that when using CosmosClient to read a document in our repository the transformation to the latest schema has already happened. Until now, this has worked well for us. However, now we have a requirement where we need to update the JObject from an external resource by doing a network call. If FromStream was async it would have made things much easier for us.
But, now we have a requirement where we need to get

authors: LeroyK MagnusJohansson ankitvijay kirankumarkolli martincostello


text:
Add small login error-handling improvements

Log when access token retrieval fails. The error currently looks like:
"http call(%s)(%s) error: reply status code was %d:\n%s", req.URL.String(), req.Method, reply.StatusCode, sd

which is safe for logging.
Add additional safety-nets to prevent users from getting into stale subscriptions due to cross-account logins.
Fixes #1609

Azure Dev CLI Install Instructions
Install scripts
MacOS/Linux

May elevate using sudo on some platforms and configurations

bash:
curl -fsSL https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1654/uninstall-azd.sh | bash;
curl -fsSL https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1654/install-azd.sh | bash -s -- --base-url https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1654 --version '' --verbose

pwsh:
Invoke-RestMethod 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1654/uninstall-azd.ps1' -OutFile uninstall-azd.ps1; ./uninstall-azd.ps1
Invoke-RestMethod 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1654/install-azd.ps1' -OutFile install-azd.ps1; ./install-azd.ps1 -BaseUrl 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1654' -Version '' -Verbose

Windows
PowerShell install
powershell -c "Set-ExecutionPolicy Bypass Process; irm 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1654/uninstall-azd.ps1' > uninstall-azd.ps1; ./uninstall-azd.ps1;"
powershell -c "Set-ExecutionPolicy Bypass Process; irm 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1654/install-azd.ps1' > install-azd.ps1; ./install-azd.ps1 -BaseUrl 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1654' -Version '' -Verbose;"

MSI install
powershell -c "irm 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1654/azd-windows-amd64.msi' -OutFile azd-windows-amd64.msi; msiexec /i azd-windows-amd64.msi /qn"

Standalone Binary

Linux -

x86_64 - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1654/azd-linux-amd64.tar.gz
ARM64 - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1654/azd-linux-arm64.tar.gz

MacOS -

x86_64 - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1654/azd-darwin-amd64.zip
ARM64 - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1654/azd-darwin-arm64.zip

Windows - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1654/azd-windows-amd64.zip

MSI

https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/1654/azd-windows-amd64.msi

Container
docker run -it azdevcliextacr.azurecr.io/azure-dev:pr-1654

Documentation

learn.microsoft.com documentation

title: Azure Developer CLI reference (preview)
description: This article explains the syntax and parameters for the various Azure Developer CLI Preview commands.
author: hhunter-ms
ms.author: hannahhunter
ms.date: 03/03/2023
ms.service: azure-dev-cli
ms.topic: conceptual
ms.custom: devx-track-azdevcli
Azure Developer CLI reference (preview)
This article explains the syntax and parameters for the various Azure Developer CLI Preview commands.
azd
Azure Developer CLI (azd) is a command-line interface for developers who build Azure solutions.
Synopsis
To begin working with Azure Developer CLI, run the azd up command by supplying a sample template in an empty directory:
	azd up –-template todo-nodejs-mongo

You can pick a template by running azd template list and then supplying the repo name as a value to --template.
The most common next commands are:
	azd pipeline config
	azd deploy
	azd monitor --overview

For more information, visit the Azure Developer CLI Dev Hub: https://aka.ms/azure-dev/devhub.
Options
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
  -h, --help         Gets help for azd.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd config: Manage the Azure Developer CLI user configuration.
azd deploy: Deploy the app's code to Azure.
azd down: Delete Azure resources for an app.
azd env: Manage environments.
azd infra: Manage Azure resources.
azd init: Initialize a new app.
azd login: Log in to Azure.
azd logout: Log out of Azure
azd monitor: Monitor a deployed app.
azd pipeline: Manage GitHub Actions or Azure Pipelines.
azd provision: Provision the Azure resources for an app.
azd restore: Restore app dependencies.
azd template: Manage templates.
azd up: Initialize the app, provision Azure resources, and deploy your project with a single command.
azd version: Print the version number of Azure Developer CLI.

azd config
Manage the Azure Developer CLI user configuration.
Synopsis
Manage the Azure Developer CLI user configuration, which includes your default Azure subscription and location.
Available since azure-dev-cli_0.4.0-beta.1.
The easiest way to configure azd for the first time is to run azd init. The subscription and location you select will be stored in the config.json file located in the config directory. To configure azd anytime afterwards, you'll use azd config set.
The default value of the config directory is:

$HOME/.azd on Linux and macOS
%USERPROFILE%.azd on Windows

The configuration directory can be overridden by specifying a path in the AZD_CONFIG_DIR environment variable.
Options
  -h, --help   Gets help for config.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd config get: Gets a configuration
azd config list: Lists all configuration values
azd config reset: Resets configuration to default
azd config set: Sets a configuration
azd config unset: Unsets a configuration
Back to top

azd config get
Gets a configuration
Synopsis
Gets a configuration in the configuration path.
The default value of the config directory is:

$HOME/.azd on Linux and macOS
%USERPROFILE%\.azd on Windows

The configuration directory can be overridden by specifying a path in the AZD_CONFIG_DIR environment variable.
azd config get <path> [flags]

Options
  -h, --help            Gets help for get.
  -o, --output string   The output format (the supported formats are json). (default "json")

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd config: Manage the Azure Developer CLI user configuration.
Back to top

azd config list
Lists all configuration values
Synopsis
Lists all configuration values in the configuration path.
The default value of the config directory is:

$HOME/.azd on Linux and macOS
%USERPROFILE%\.azd on Windows

The configuration directory can be overridden by specifying a path in the AZD_CONFIG_DIR environment variable.
azd config list [flags]

Options
  -h, --help            Gets help for list.
  -o, --output string   The output format (the supported formats are json). (default "json")

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd config: Manage the Azure Developer CLI user configuration.
Back to top

azd config reset
Resets configuration to default
Synopsis
Resets all configuration in the configuration path.
The default value of the config directory is:

$HOME/.azd on Linux and macOS
%USERPROFILE%\.azd on Windows

The configuration directory can be overridden by specifying a path in the AZD_CONFIG_DIR environment variable to the default.
azd config reset [flags]

Options
  -h, --help   Gets help for reset.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd config: Manage the Azure Developer CLI user configuration.
Back to top

azd config set
Sets a configuration
Synopsis
Sets a configuration in the configuration path.
The default value of the config directory is:

$HOME/.azd on Linux and macOS
%USERPROFILE%\.azd on Windows

The configuration directory can be overridden by specifying a path in the AZD_CONFIG_DIR environment variable.
azd config set <path> <value> [flags]

Examples
azd config set defaults.subscription <yourSubscriptionID>
azd config set defaults.location eastus

Options
  -h, --help   Gets help for set.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd config: Manage the Azure Developer CLI user configuration.
Back to top

azd config unset
Unsets a configuration
Synopsis
Removes a configuration in the configuration path.
The default value of the config directory is:

$HOME/.azd on Linux and macOS
%USERPROFILE%\.azd on Windows

The configuration directory can be overridden by specifying a path in the AZD_CONFIG_DIR environment variable.
azd config unset <path> [flags]

Examples
azd config unset defaults.location

Options
  -h, --help   Gets help for unset.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd config: Manage the Azure Developer CLI user configuration.
Back to top

azd deploy
Deploy the app's code to Azure.
Synopsis
Deploy the app's code to Azure.
When no --service value is specified, all services in the azure.yaml file (found in the root of your project) are deployed.
Examples:
	azd deploy
	azd deploy --service api
	azd deploy --service web

After the deployment is complete, the endpoint is printed. To start the service, select the endpoint or paste it in a browser.
azd deploy [flags]

Options
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for deploy.
  -o, --output string        The output format (the supported formats are json, none). (default "none")
      --service string       Deploys a specific service (when the string is unspecified, all services that are listed in the azure.yaml file are deployed).

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd down
Delete Azure resources for an app.
azd down [flags]

Options
  -e, --environment string   The name of the environment to use.
      --force                Does not require confirmation before it deletes resources.
  -h, --help                 Gets help for down.
  -o, --output string        The output format (the supported formats are json, none). (default "none")
      --purge                Does not require confirmation before it permanently deletes resources that are soft-deleted by default (for example, key vaults).

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd env
Manage environments.
Synopsis
Manage environments.
With this command group, you can create a new environment or get, set, and list your app environments. An app can have multiple environments (for example, dev, test, prod), each with a different configuration (that is, connectivity information) for accessing Azure resources.
You can find all environment configurations under the .azure\<environment-name> directories. The environment name is stored as the AZURE_ENV_NAME environment variable in the .azure\<environment-name>\directory\.env file.
Options
  -h, --help   Gets help for env.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd env get-values: Get all environment values.
azd env list: List environments.
azd env new: Create a new environment.
azd env refresh: Refresh environment settings by using information from a previous infrastructure provision.
azd env select: Set the default environment.
azd env set: Set a value in the environment.
Back to top

azd env get-values
Get all environment values.
azd env get-values [flags]

Options
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for get-values.
  -o, --output string        The output format (the supported formats are json, dotenv). (default "dotenv")

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd env: Manage environments.
Back to top

azd env list
List environments.
azd env list [flags]

Options
  -h, --help            Gets help for list.
  -o, --output string   The output format (the supported formats are json, table). (default "table")

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd env: Manage environments.
Back to top

azd env new
Create a new environment.
azd env new <environment> [flags]

Options
  -h, --help                  Gets help for new.
  -l, --location string       Azure location for the new environment
      --subscription string   Name or ID of an Azure subscription to use for the new environment

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd env: Manage environments.
Back to top

azd env refresh
Refresh environment settings by using information from a previous infrastructure provision.
azd env refresh [flags]

Options
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for refresh.
  -o, --output string        The output format (the supported formats are json, none). (default "none")

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd env: Manage environments.
Back to top

azd env select
Set the default environment.
azd env select <environment> [flags]

Options
  -h, --help   Gets help for select.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd env: Manage environments.
Back to top

azd env set
Set a value in the environment.
azd env set <key> <value> [flags]

Options
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for set.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd env: Manage environments.
Back to top

azd infra
Manage Azure resources.
Options
  -h, --help   Gets help for infra.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd infra create: Provision the Azure resources for an app.
azd infra delete: Delete Azure resources for an app.
Back to top

azd infra create
Provision the Azure resources for an app.
Synopsis
Provision the Azure resources for an app.
The command prompts you for the following values:

Environment name: The name of your environment.
Azure location: The Azure location where your resources will be deployed.
Azure subscription: The Azure subscription where your resources will be deployed.

Depending on what Azure resources are created, running this command might take a while. To view progress, go to the Azure portal and search for the resource group that contains your environment name.
azd infra create [flags]

Options
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for create.
      --no-progress          Suppresses progress information.
  -o, --output string        The output format (the supported formats are json, none). (default "none")

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd infra: Manage Azure resources.
Back to top

azd infra delete
Delete Azure resources for an app.
azd infra delete [flags]

Options
  -e, --environment string   The name of the environment to use.
      --force                Does not require confirmation before it deletes resources.
  -h, --help                 Gets help for delete.
  -o, --output string        The output format (the supported formats are json, none). (default "none")
      --purge                Does not require confirmation before it permanently deletes resources that are soft-deleted by default (for example, key vaults).

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd infra: Manage Azure resources.
Back to top

azd init
Initialize a new app.
Synopsis
Initialize a new app.
When no template is supplied, you can optionally select an Azure Developer CLI template for cloning. Otherwise, azd init initializes the current directory and creates resources so that your project is compatible with Azure Developer CLI.
When a template is provided, the sample code is cloned to the current directory.
azd init [flags]

Options
  -b, --branch string         The template branch to initialize from.
  -e, --environment string    The name of the environment to use.
  -h, --help                  Gets help for init.
  -l, --location string       Azure location for the new environment
      --subscription string   Name or ID of an Azure subscription to use for the new environment
  -t, --template string       The template to use when you initialize the project. You can use Full URI, <owner>/<repository>, or <repository> if it's part of the azure-samples organization.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd login
Log in to Azure.
Synopsis
Log in to Azure.
When run without any arguments, log in interactively using a browser. To log in using a device code, pass
--use-device-code.
To log in as a service principal, pass --client-id and --tenant-id as well as one of: --client-secret,
--client-certificate, --federated-credential, or --federated-credential-provider.
azd login [flags]

Options
      --check-status                           Checks the log-in status instead of logging in.
      --client-certificate string              The path to the client certificate for the service principal to authenticate with.
      --client-id string                       The client id for the service principal to authenticate with.
      --client-secret string                   The client secret for the service principal to authenticate with. Set to the empty string to read the value from the console.
      --federated-credential string            The federated token for the service principal to authenticate with. Set to the empty string to read the value from the console.
      --federated-credential-provider string   The provider to use to acquire a federated token to authenticate with.
  -h, --help                                   Gets help for login.
  -o, --output string                          The output format (the supported formats are json, none). (default "none")
      --redirect-port int                      Choose the port to be used as part of the redirect URI during interactive login.
      --tenant-id string                       The tenant id or domain name to authenticate with.
      --use-device-code                        When true, log in by using a device code instead of a browser.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd logout
Log out of Azure
Synopsis
Log out of Azure
azd logout [flags]

Options
  -h, --help   Gets help for logout.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd monitor
Monitor a deployed app.
Synopsis
Monitor a deployed app.
Examples:
	azd monitor --overview
	azd monitor -–live
	azd monitor --logs

For more information, go to https://aka.ms/azure-dev/monitor.
azd monitor [flags]

Options
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for monitor.
      --live                 Open a browser to Application Insights Live Metrics. Live Metrics is currently not supported for Python apps.
      --logs                 Open a browser to Application Insights Logs.
      --overview             Open a browser to Application Insights Overview Dashboard.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd pipeline
Manage GitHub Actions or Azure Pipelines.
Synopsis
Manage GitHub Actions or Azure Pipelines.
The Azure Developer CLI template includes a GitHub Actions and an Azure Pipeline configuration file in the .github/workflows and .azdo/pipelines directories respectively. The configuration file deploys your app whenever code is pushed to the main branch.
For more information, go to https://aka.ms/azure-dev/pipeline.
Options
  -h, --help   Gets help for pipeline.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd pipeline config: Create and configure your deployment pipeline by using GitHub Actions or Azure Pipelines.
Back to top

azd pipeline config
Create and configure your deployment pipeline by using GitHub Actions or Azure Pipelines.
Synopsis
Create and configure your deployment pipeline by using GitHub Actions or Azure Pipelines.
For more information, go to https://aka.ms/azure-dev/pipeline.
azd pipeline config [flags]

Options
      --auth-type string        The authentication type used between the pipeline provider and Azure for deployment (Only valid for GitHub provider)
  -e, --environment string      The name of the environment to use.
  -h, --help                    Gets help for config.
      --principal-name string   The name of the service principal to use to grant access to Azure resources as part of the pipeline.
      --principal-role string   The role to assign to the service principal. (default "contributor")
      --provider string         The pipeline provider to use (github for Github Actions and azdo for Azure Pipelines). (default "github")
      --remote-name string      The name of the git remote to configure the pipeline to run on. (default "origin")

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd pipeline: Manage GitHub Actions or Azure Pipelines.
Back to top

azd provision
Provision the Azure resources for an app.
Synopsis
Provision the Azure resources for an app.
The command prompts you for the following values:

Environment name: The name of your environment.
Azure location: The Azure location where your resources will be deployed.
Azure subscription: The Azure subscription where your resources will be deployed.

Depending on what Azure resources are created, running this command might take a while. To view progress, go to the Azure portal and search for the resource group that contains your environment name.
azd provision [flags]

Options
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for provision.
      --no-progress          Suppresses progress information.
  -o, --output string        The output format (the supported formats are json, none). (default "none")

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd restore
Restore app dependencies.
Synopsis
Restore app dependencies.
Run this command to download and install all the required libraries so that you can build, run, and debug the app locally.
For the best local run and debug experience, go to https://aka.ms/azure-dev/vscode to learn how to use the Visual Studio Code extension.
azd restore [flags]

Options
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for restore.
      --service string       Restores a specific service (when the string is unspecified, all services that are listed in the azure.yaml file are restored).

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd template
Manage templates.
Options
  -h, --help   Gets help for template.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd template list: List templates.
azd template show: Show the template details.
Back to top

azd template list
List templates.
azd template list [flags]

Options
  -h, --help            Gets help for list.
  -o, --output string   The output format (the supported formats are json, table). (default "table")

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd template: Manage templates.
Back to top

azd template show
Show the template details.
azd template show <template> [flags]

Options
  -h, --help            Gets help for show.
  -o, --output string   The output format (the supported formats are json, table). (default "table")

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

azd template: Manage templates.
Back to top

azd up
Initialize the app, provision Azure resources, and deploy your project with a single command.
Synopsis
Initialize the project (if the project folder has not been initialized or cloned from a template), provision Azure resources, and deploy your project with a single command.
This command executes the following in one step:
	azd init
	azd provision
	azd deploy

When no template is supplied, you can optionally select an Azure Developer CLI template for cloning. Otherwise, running azd up initializes the current directory so that your project is compatible with Azure Developer CLI.
azd up [flags]

Options
  -b, --branch string         The template branch to initialize from.
  -e, --environment string    The name of the environment to use.
  -h, --help                  Gets help for up.
  -l, --location string       Azure location for the new environment
      --no-progress           Suppresses progress information.
  -o, --output string         The output format (the supported formats are json, none). (default "none")
      --service string        Deploys a specific service (when the string is unspecified, all services that are listed in the azure.yaml file are deployed).
      --subscription string   Name or ID of an Azure subscription to use for the new environment
  -t, --template string       The template to use when you initialize the project. You can use Full URI, <owner>/<repository>, or <repository> if it's part of the azure-samples organization.

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

azd version
Print the version number of Azure Developer CLI.
azd version [flags]

Options
  -h, --help            Gets help for version.
  -o, --output string   The output format (the supported formats are json, none). (default "none")

Options inherited from parent commands
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --no-prompt    Accepts the default value instead of prompting, or it fails if there is no default.

See also

Back to top

source: gharchive/pull-request

authors: azure-sdk weikanglim

repo: Azure/azure-dev

license: MIT

license_type: permissive

license_source: github-api


text:
Fix Playwright test fail in todo-nodejs-mongo

Fixes issue https://github.com/Azure/azure-dev/issues/246
Change files: templates/todo/common/tests/todo.spec.ts
Add setTimeOut is used to wait for the page data to full load.
@rajeshkamal5050 for notification.

I think it's better to pass { waitUntil: 'networkidle' } to the initial page.goto call as an option. So the code has now been corrected according to this idea.

pipeline is currently broken after this PR:
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1814636&view=logs&j=9392ca66-1ee4-52af-022d-b22076a99114&t=6db148d5-c790-543c-3e98-57830bb8eafe&l=162
Change:

@hongli750210 , any ideas?

@vhvb1989
Replace ： with :  to fix the problem you mentioned. Can I still upload a new version after the code has been merged?

@hongli750210 additional syntax fix was made by @ellismg. Should be good now.

https://github.com/Azure/azure-dev/pull/546


text:
Create Environment failing on Get-Member cmdlet

Creating a environment from a ARM template using the Create environment task fails on a Get-Member cmdlet somwhere in the task, i have not yet been able to test the other tasks. It seems to happen with every Template i try, i have been testing with some custom templates (https://github.com/InsaneNL/azurearmtemplate) and the quickstart templates (https://github.com/Azure/azure-quickstart-templates).
AzurePSCmdletsVersion= 6.13.1
PSVersion = 5.1.17763.316
019-05-13T06:48:06.1464466Z Parameters = [not displayed for security reasons]
2019-05-13T06:48:06.1476956Z TemplateOutputVariables = false
2019-05-13T06:48:06.1809797Z Creating Environment with parameters
2019-05-13T06:48:08.5007368Z Completing Azure DevTest Labs Create Environment Task
2019-05-13T06:48:08.5285322Z ##[error]System.Management.Automation.ActionPreferenceStopException: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop:
2019-05-13T06:48:08.5295534Z You must specify an object for the Get-Member cmdlet.
2019-05-13T06:48:08.5295951Z at System.Management.Automation.Runspaces.PipelineBase.Invoke(IEnumerable input)
2019-05-13T06:48:08.5296381Z at System.Management.Automation.PowerShell.Worker.ConstructPipelineAndDoWork(Runspace rs, Boolean performSyncInvoke)
2019-05-13T06:48:08.5296905Z at System.Management.Automation.PowerShell.Worker.CreateRunspaceIfNeededAndDoWork(Runspace rsToUse, Boolean isSync)
2019-05-13T06:48:08.5297478Z at System.Management.Automation.PowerShell.CoreInvokeHelper[TInput,TOutput](PSDataCollection1 input, PSDataCollection1 output, PSInvocationSettings settings)
2019-05-13T06:48:08.5298126Z at System.Management.Automation.PowerShell.CoreInvoke[TInput,TOutput](PSDataCollection1 input, PSDataCollection1 output, PSInvocationSettings settings)
2019-05-13T06:48:08.5298732Z at Microsoft.TeamFoundation.DistributedTask.Handlers.LegacyVSTSPowerShellHost.VSTSPowerShellHost.Main(String[] args)
2019-05-13T06:48:08.5660169Z ##[error]LegacyVSTSPowerShellHost.exe completed with return code: -1.

@InsaneNL, thank you for reporting the issue. Give me some time to repro and get back to you.

I have validated the task with the latest Azure PS (i.e. Azure v5.3.0 and AzureRM v6.13.1) and all seems good. I am therefore not able to repro what you reported.
I will close this issue, but feel free to re-open it. If you do, please provide me a sample environment and include the parameters you use. I need to have as many details as possible to repro the case; otherwise, I will not be able to help.

sorry, i didn't see the edit to your first comment, i tried that now with the WebApp template from the public environment repo and it fails as well on the same "you must specify an object for the Get-Member cmdlet" error. We run TFS 2018(16.131.27701.1) and the build server is a fresh Windows Server 2019 installation with PowerShell 5.1.17763.316, the TFS agent, Azure v5.3.0, AzureRM v6.13.1 and Google Chrome installed. Is there anything I could be missing that may cause this?

@InsaneNL, reach out to me via email (leov at microsoft dot com). Let's set up time to look at this together.

source: gharchive/issue

authors: InsaneNL leovms

repo: Azure/azure-devtestlab

license: mit

license_source: bigquery


text:
[Do not merge] Update document with profiles (Just for review, do not merge)

TOC files in this pull request are separated by profiles. And the TOC file for repo latest is  TOC_latest.md and the TOC file for repo 2017-03-09-profile is TOC_2017-03-09-profile.md.
This pull request is just used for review. Please do not merge.

@georgechenchao,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

:warning: Validation status: warnings

File
Status
Preview URL
Details

docs-ref-autogen/2017-03-09-profile/acr/credential.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/acs/dcos.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/acs/kubernetes.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/ad/group/member.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/ad/sp.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/ad/user.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/appservice/plan.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/batch/account/keys.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/batch/application.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/batch/application/package.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/batch/application/summary.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/batch/certificate.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/batch/job-schedule.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/batch/job/all-statistics.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/batch/job/prep-release-status.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/batch/location.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/batch/node/remote-desktop.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/batch/node/remote-login-settings.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/batch/node/scheduling.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/batch/node/user.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/batch/pool/all-statistics.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/batch/pool/autoscale.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/batch/pool/usage-metrics.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/batch/task/file.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/billing/period.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/cdn/custom-domain.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/cdn/origin.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/cdn/profile.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/cognitiveservices/account.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/cognitiveservices/account/keys.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/consumption/usage.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/cosmosdb.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/cosmosdb/collection.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/dla.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/dla/account/data-lake-store.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/dla/account/firewall.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/dla/catalog.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/dla/catalog/database.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/dla/catalog/external-data-source.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/dla/catalog/package.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/dla/catalog/procedure.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/dla/catalog/schema.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/dla/catalog/table-partition.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/dla/catalog/table-stats.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/dla/catalog/table-type.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/dla/job.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/dla/job/recurrence.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/dls.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/dls/account.pycliyml
:warning:Warning
View
Details

docs-ref-autogen/2017-03-09-profile/dls/account/firewall.pycliyml
:warning:Warning
View
Details

This comment lists only the first 50 files in the pull request.

docs-ref-autogen/2017-03-09-profile/acr/credential.pycliyml

[Warning] Uid(az_acr_credential) has already been defined in docs-ref-autogen/latest/acr/credential.pycliyml.
[Warning] Uid(az_acr_credential_renew) has already been defined in docs-ref-autogen/latest/acr/credential.pycliyml.
[Warning] Uid(az_acr_credential_show) has already been defined in docs-ref-autogen/latest/acr/credential.pycliyml.

docs-ref-autogen/2017-03-09-profile/acs/dcos.pycliyml

[Warning] Uid(az_acs_dcos) has already been defined in docs-ref-autogen/latest/acs/dcos.pycliyml.
[Warning] Uid(az_acs_dcos_browse) has already been defined in docs-ref-autogen/latest/acs/dcos.pycliyml.
[Warning] Uid(az_acs_dcos_install-cli) has already been defined in docs-ref-autogen/latest/acs/dcos.pycliyml.

docs-ref-autogen/2017-03-09-profile/acs/kubernetes.pycliyml

[Warning] Uid(az_acs_kubernetes) has already been defined in docs-ref-autogen/latest/acs/kubernetes.pycliyml.
[Warning] Uid(az_acs_kubernetes_browse) has already been defined in docs-ref-autogen/latest/acs/kubernetes.pycliyml.
[Warning] Uid(az_acs_kubernetes_get-credentials) has already been defined in docs-ref-autogen/latest/acs/kubernetes.pycliyml.
[Warning] Uid(az_acs_kubernetes_install-cli) has already been defined in docs-ref-autogen/latest/acs/kubernetes.pycliyml.

docs-ref-autogen/2017-03-09-profile/ad/group/member.pycliyml

[Warning] Uid(az_ad_group_member) has already been defined in docs-ref-autogen/latest/ad/group/member.pycliyml.
[Warning] Uid(az_ad_group_member_add) has already been defined in docs-ref-autogen/latest/ad/group/member.pycliyml.
[Warning] Uid(az_ad_group_member_check) has already been defined in docs-ref-autogen/latest/ad/group/member.pycliyml.
[Warning] Uid(az_ad_group_member_list) has already been defined in docs-ref-autogen/latest/ad/group/member.pycliyml.
[Warning] Uid(az_ad_group_member_remove) has already been defined in docs-ref-autogen/latest/ad/group/member.pycliyml.

docs-ref-autogen/2017-03-09-profile/ad/sp.pycliyml

[Warning] Uid(az_ad_sp) has already been defined in docs-ref-autogen/latest/ad/sp.pycliyml.
[Warning] Uid(az_ad_sp_create) has already been defined in docs-ref-autogen/latest/ad/sp.pycliyml.
[Warning] Uid(az_ad_sp_create-for-rbac) has already been defined in docs-ref-autogen/latest/ad/sp.pycliyml.
[Warning] Uid(az_ad_sp_delete) has already been defined in docs-ref-autogen/latest/ad/sp.pycliyml.
[Warning] Uid(az_ad_sp_list) has already been defined in docs-ref-autogen/latest/ad/sp.pycliyml.
[Warning] Uid(az_ad_sp_reset-credentials) has already been defined in docs-ref-autogen/latest/ad/sp.pycliyml.
[Warning] Uid(az_ad_sp_show) has already been defined in docs-ref-autogen/latest/ad/sp.pycliyml.

docs-ref-autogen/2017-03-09-profile/ad/user.pycliyml

[Warning] Uid(az_ad_user) has already been defined in docs-ref-autogen/latest/ad/user.pycliyml.
[Warning] Uid(az_ad_user_create) has already been defined in docs-ref-autogen/latest/ad/user.pycliyml.
[Warning] Uid(az_ad_user_delete) has already been defined in docs-ref-autogen/latest/ad/user.pycliyml.
[Warning] Uid(az_ad_user_list) has already been defined in docs-ref-autogen/latest/ad/user.pycliyml.
[Warning] Uid(az_ad_user_show) has already been defined in docs-ref-autogen/latest/ad/user.pycliyml.

docs-ref-autogen/2017-03-09-profile/appservice/plan.pycliyml

[Warning] Uid(az_appservice_plan) has already been defined in docs-ref-autogen/latest/appservice/plan.pycliyml.
[Warning] Uid(az_appservice_plan_create) has already been defined in docs-ref-autogen/latest/appservice/plan.pycliyml.
[Warning] Uid(az_appservice_plan_delete) has already been defined in docs-ref-autogen/latest/appservice/plan.pycliyml.
[Warning] Uid(az_appservice_plan_list) has already been defined in docs-ref-autogen/latest/appservice/plan.pycliyml.
[Warning] Uid(az_appservice_plan_show) has already been defined in docs-ref-autogen/latest/appservice/plan.pycliyml.
[Warning] Uid(az_appservice_plan_update) has already been defined in docs-ref-autogen/latest/appservice/plan.pycliyml.

docs-ref-autogen/2017-03-09-profile/batch/account/keys.pycliyml

[Warning] Uid(az_batch_account_keys) has already been defined in docs-ref-autogen/latest/batch/account/keys.pycliyml.
[Warning] Uid(az_batch_account_keys_list) has already been defined in docs-ref-autogen/latest/batch/account/keys.pycliyml.
[Warning] Uid(az_batch_account_keys_renew) has already been defined in docs-ref-autogen/latest/batch/account/keys.pycliyml.

docs-ref-autogen/2017-03-09-profile/batch/application.pycliyml

[Warning] Uid(az_batch_application) has already been defined in docs-ref-autogen/latest/batch/application.pycliyml.
[Warning] Uid(az_batch_application_create) has already been defined in docs-ref-autogen/latest/batch/application.pycliyml.
[Warning] Uid(az_batch_application_delete) has already been defined in docs-ref-autogen/latest/batch/application.pycliyml.
[Warning] Uid(az_batch_application_list) has already been defined in docs-ref-autogen/latest/batch/application.pycliyml.
[Warning] Uid(az_batch_application_set) has already been defined in docs-ref-autogen/latest/batch/application.pycliyml.
[Warning] Uid(az_batch_application_show) has already been defined in docs-ref-autogen/latest/batch/application.pycliyml.

docs-ref-autogen/2017-03-09-profile/batch/application/package.pycliyml

[Warning] Uid(az_batch_application_package) has already been defined in docs-ref-autogen/latest/batch/application/package.pycliyml.
[Warning] Uid(az_batch_application_package_activate) has already been defined in docs-ref-autogen/latest/batch/application/package.pycliyml.
[Warning] Uid(az_batch_application_package_create) has already been defined in docs-ref-autogen/latest/batch/application/package.pycliyml.
[Warning] Uid(az_batch_application_package_delete) has already been defined in docs-ref-autogen/latest/batch/application/package.pycliyml.
[Warning] Uid(az_batch_application_package_show) has already been defined in docs-ref-autogen/latest/batch/application/package.pycliyml.

docs-ref-autogen/2017-03-09-profile/batch/application/summary.pycliyml

[Warning] Uid(az_batch_application_summary) has already been defined in docs-ref-autogen/latest/batch/application/summary.pycliyml.
[Warning] Uid(az_batch_application_summary_list) has already been defined in docs-ref-autogen/latest/batch/application/summary.pycliyml.
[Warning] Uid(az_batch_application_summary_show) has already been defined in docs-ref-autogen/latest/batch/application/summary.pycliyml.

docs-ref-autogen/2017-03-09-profile/batch/certificate.pycliyml

[Warning] Uid(az_batch_certificate) has already been defined in docs-ref-autogen/latest/batch/certificate.pycliyml.
[Warning] Uid(az_batch_certificate_create) has already been defined in docs-ref-autogen/latest/batch/certificate.pycliyml.
[Warning] Uid(az_batch_certificate_delete) has already been defined in docs-ref-autogen/latest/batch/certificate.pycliyml.
[Warning] Uid(az_batch_certificate_list) has already been defined in docs-ref-autogen/latest/batch/certificate.pycliyml.
[Warning] Uid(az_batch_certificate_show) has already been defined in docs-ref-autogen/latest/batch/certificate.pycliyml.

docs-ref-autogen/2017-03-09-profile/batch/job-schedule.pycliyml

[Warning] Uid(az_batch_job-schedule) has already been defined in docs-ref-autogen/latest/batch/job-schedule.pycliyml.
[Warning] Uid(az_batch_job-schedule_create) has already been defined in docs-ref-autogen/latest/batch/job-schedule.pycliyml.
[Warning] Uid(az_batch_job-schedule_delete) has already been defined in docs-ref-autogen/latest/batch/job-schedule.pycliyml.
[Warning] Uid(az_batch_job-schedule_disable) has already been defined in docs-ref-autogen/latest/batch/job-schedule.pycliyml.
[Warning] Uid(az_batch_job-schedule_enable) has already been defined in docs-ref-autogen/latest/batch/job-schedule.pycliyml.
[Warning] Uid(az_batch_job-schedule_list) has already been defined in docs-ref-autogen/latest/batch/job-schedule.pycliyml.
[Warning] Uid(az_batch_job-schedule_reset) has already been defined in docs-ref-autogen/latest/batch/job-schedule.pycliyml.
[Warning] Uid(az_batch_job-schedule_set) has already been defined in docs-ref-autogen/latest/batch/job-schedule.pycliyml.
[Warning] Uid(az_batch_job-schedule_show) has already been defined in docs-ref-autogen/latest/batch/job-schedule.pycliyml.
[Warning] Uid(az_batch_job-schedule_stop) has already been defined in docs-ref-autogen/latest/batch/job-schedule.pycliyml.

docs-ref-autogen/2017-03-09-profile/batch/job/all-statistics.pycliyml

[Warning] Uid(az_batch_job_all-statistics) has already been defined in docs-ref-autogen/latest/batch/job/all-statistics.pycliyml.
[Warning] Uid(az_batch_job_all-statistics_show) has already been defined in docs-ref-autogen/latest/batch/job/all-statistics.pycliyml.

docs-ref-autogen/2017-03-09-profile/batch/job/prep-release-status.pycliyml

[Warning] Uid(az_batch_job_prep-release-status) has already been defined in docs-ref-autogen/latest/batch/job/prep-release-status.pycliyml.
[Warning] Uid(az_batch_job_prep-release-status_list) has already been defined in docs-ref-autogen/latest/batch/job/prep-release-status.pycliyml.

docs-ref-autogen/2017-03-09-profile/batch/location.pycliyml

[Warning] Uid(az_batch_location) has already been defined in docs-ref-autogen/latest/batch/location.pycliyml.

docs-ref-autogen/2017-03-09-profile/batch/node/remote-desktop.pycliyml

[Warning] Uid(az_batch_node_remote-desktop) has already been defined in docs-ref-autogen/latest/batch/node/remote-desktop.pycliyml.
[Warning] Uid(az_batch_node_remote-desktop_download) has already been defined in docs-ref-autogen/latest/batch/node/remote-desktop.pycliyml.

docs-ref-autogen/2017-03-09-profile/batch/node/remote-login-settings.pycliyml

[Warning] Uid(az_batch_node_remote-login-settings) has already been defined in docs-ref-autogen/latest/batch/node/remote-login-settings.pycliyml.
[Warning] Uid(az_batch_node_remote-login-settings_show) has already been defined in docs-ref-autogen/latest/batch/node/remote-login-settings.pycliyml.

docs-ref-autogen/2017-03-09-profile/batch/node/scheduling.pycliyml

[Warning] Uid(az_batch_node_scheduling) has already been defined in docs-ref-autogen/latest/batch/node/scheduling.pycliyml.
[Warning] Uid(az_batch_node_scheduling_disable) has already been defined in docs-ref-autogen/latest/batch/node/scheduling.pycliyml.
[Warning] Uid(az_batch_node_scheduling_enable) has already been defined in docs-ref-autogen/latest/batch/node/scheduling.pycliyml.

docs-ref-autogen/2017-03-09-profile/batch/node/user.pycliyml

[Warning] Uid(az_batch_node_user) has already been defined in docs-ref-autogen/latest/batch/node/user.pycliyml.
[Warning] Uid(az_batch_node_user_create) has already been defined in docs-ref-autogen/latest/batch/node/user.pycliyml.
[Warning] Uid(az_batch_node_user_delete) has already been defined in docs-ref-autogen/latest/batch/node/user.pycliyml.
[Warning] Uid(az_batch_node_user_reset) has already been defined in docs-ref-autogen/latest/batch/node/user.pycliyml.

docs-ref-autogen/2017-03-09-profile/batch/pool/all-statistics.pycliyml

[Warning] Uid(az_batch_pool_all-statistics) has already been defined in docs-ref-autogen/latest/batch/pool/all-statistics.pycliyml.
[Warning] Uid(az_batch_pool_all-statistics_show) has already been defined in docs-ref-autogen/latest/batch/pool/all-statistics.pycliyml.

docs-ref-autogen/2017-03-09-profile/batch/pool/autoscale.pycliyml

[Warning] Uid(az_batch_pool_autoscale) has already been defined in docs-ref-autogen/latest/batch/pool/autoscale.pycliyml.
[Warning] Uid(az_batch_pool_autoscale_disable) has already been defined in docs-ref-autogen/latest/batch/pool/autoscale.pycliyml.
[Warning] Uid(az_batch_pool_autoscale_enable) has already been defined in docs-ref-autogen/latest/batch/pool/autoscale.pycliyml.
[Warning] Uid(az_batch_pool_autoscale_evaluate) has already been defined in docs-ref-autogen/latest/batch/pool/autoscale.pycliyml.

docs-ref-autogen/2017-03-09-profile/batch/pool/usage-metrics.pycliyml

[Warning] Uid(az_batch_pool_usage-metrics) has already been defined in docs-ref-autogen/latest/batch/pool/usage-metrics.pycliyml.
[Warning] Uid(az_batch_pool_usage-metrics_list) has already been defined in docs-ref-autogen/latest/batch/pool/usage-metrics.pycliyml.

docs-ref-autogen/2017-03-09-profile/batch/task/file.pycliyml

[Warning] Uid(az_batch_task_file) has already been defined in docs-ref-autogen/latest/batch/task/file.pycliyml.
[Warning] Uid(az_batch_task_file_delete) has already been defined in docs-ref-autogen/latest/batch/task/file.pycliyml.
[Warning] Uid(az_batch_task_file_download) has already been defined in docs-ref-autogen/latest/batch/task/file.pycliyml.
[Warning] Uid(az_batch_task_file_list) has already been defined in docs-ref-autogen/latest/batch/task/file.pycliyml.
[Warning] Uid(az_batch_task_file_show) has already been defined in docs-ref-autogen/latest/batch/task/file.pycliyml.

docs-ref-autogen/2017-03-09-profile/billing/period.pycliyml

[Warning] Uid(az_billing_period) has already been defined in docs-ref-autogen/latest/billing/period.pycliyml.
[Warning] Uid(az_billing_period_list) has already been defined in docs-ref-autogen/latest/billing/period.pycliyml.
[Warning] Uid(az_billing_period_show) has already been defined in docs-ref-autogen/latest/billing/period.pycliyml.

docs-ref-autogen/2017-03-09-profile/cdn/custom-domain.pycliyml

[Warning] Uid(az_cdn_custom-domain) has already been defined in docs-ref-autogen/latest/cdn/custom-domain.pycliyml.
[Warning] Uid(az_cdn_custom-domain_create) has already been defined in docs-ref-autogen/latest/cdn/custom-domain.pycliyml.
[Warning] Uid(az_cdn_custom-domain_delete) has already been defined in docs-ref-autogen/latest/cdn/custom-domain.pycliyml.
[Warning] Uid(az_cdn_custom-domain_list) has already been defined in docs-ref-autogen/latest/cdn/custom-domain.pycliyml.
[Warning] Uid(az_cdn_custom-domain_show) has already been defined in docs-ref-autogen/latest/cdn/custom-domain.pycliyml.

docs-ref-autogen/2017-03-09-profile/cdn/origin.pycliyml

[Warning] Uid(az_cdn_origin) has already been defined in docs-ref-autogen/latest/cdn/origin.pycliyml.
[Warning] Uid(az_cdn_origin_list) has already been defined in docs-ref-autogen/latest/cdn/origin.pycliyml.
[Warning] Uid(az_cdn_origin_show) has already been defined in docs-ref-autogen/latest/cdn/origin.pycliyml.

docs-ref-autogen/2017-03-09-profile/cdn/profile.pycliyml

[Warning] Uid(az_cdn_profile) has already been defined in docs-ref-autogen/latest/cdn/profile.pycliyml.
[Warning] Uid(az_cdn_profile_create) has already been defined in docs-ref-autogen/latest/cdn/profile.pycliyml.
[Warning] Uid(az_cdn_profile_delete) has already been defined in docs-ref-autogen/latest/cdn/profile.pycliyml.
[Warning] Uid(az_cdn_profile_list) has already been defined in docs-ref-autogen/latest/cdn/profile.pycliyml.
[Warning] Uid(az_cdn_profile_show) has already been defined in docs-ref-autogen/latest/cdn/profile.pycliyml.
[Warning] Uid(az_cdn_profile_update) has already been defined in docs-ref-autogen/latest/cdn/profile.pycliyml.
[Warning] Uid(az_cdn_profile_usage) has already been defined in docs-ref-autogen/latest/cdn/profile.pycliyml.

docs-ref-autogen/2017-03-09-profile/cognitiveservices/account.pycliyml

[Warning] Uid(az_cognitiveservices_account) has already been defined in docs-ref-autogen/latest/cognitiveservices/account.pycliyml.
[Warning] Uid(az_cognitiveservices_account_create) has already been defined in docs-ref-autogen/latest/cognitiveservices/account.pycliyml.
[Warning] Uid(az_cognitiveservices_account_delete) has already been defined in docs-ref-autogen/latest/cognitiveservices/account.pycliyml.
[Warning] Uid(az_cognitiveservices_account_list-skus) has already been defined in docs-ref-autogen/latest/cognitiveservices/account.pycliyml.
[Warning] Uid(az_cognitiveservices_account_show) has already been defined in docs-ref-autogen/latest/cognitiveservices/account.pycliyml.
[Warning] Uid(az_cognitiveservices_account_update) has already been defined in docs-ref-autogen/latest/cognitiveservices/account.pycliyml.

docs-ref-autogen/2017-03-09-profile/cognitiveservices/account/keys.pycliyml

[Warning] Uid(az_cognitiveservices_account_keys) has already been defined in docs-ref-autogen/latest/cognitiveservices/account/keys.pycliyml.
[Warning] Uid(az_cognitiveservices_account_keys_list) has already been defined in docs-ref-autogen/latest/cognitiveservices/account/keys.pycliyml.
[Warning] Uid(az_cognitiveservices_account_keys_regenerate) has already been defined in docs-ref-autogen/latest/cognitiveservices/account/keys.pycliyml.

docs-ref-autogen/2017-03-09-profile/consumption/usage.pycliyml

[Warning] Uid(az_consumption_usage) has already been defined in docs-ref-autogen/latest/consumption/usage.pycliyml.
[Warning] Uid(az_consumption_usage_list) has already been defined in docs-ref-autogen/latest/consumption/usage.pycliyml.

docs-ref-autogen/2017-03-09-profile/cosmosdb.pycliyml

[Warning] Uid(az_cosmosdb) has already been defined in docs-ref-autogen/latest/cosmosdb.pycliyml.
[Warning] Uid(az_cosmosdb_check-name-exists) has already been defined in docs-ref-autogen/latest/cosmosdb.pycliyml.
[Warning] Uid(az_cosmosdb_create) has already been defined in docs-ref-autogen/latest/cosmosdb.pycliyml.
[Warning] Uid(az_cosmosdb_delete) has already been defined in docs-ref-autogen/latest/cosmosdb.pycliyml.
[Warning] Uid(az_cosmosdb_failover-priority-change) has already been defined in docs-ref-autogen/latest/cosmosdb.pycliyml.
[Warning] Uid(az_cosmosdb_list) has already been defined in docs-ref-autogen/latest/cosmosdb.pycliyml.
[Warning] Uid(az_cosmosdb_list-connection-strings) has already been defined in docs-ref-autogen/latest/cosmosdb.pycliyml.
[Warning] Uid(az_cosmosdb_list-keys) has already been defined in docs-ref-autogen/latest/cosmosdb.pycliyml.
[Warning] Uid(az_cosmosdb_list-read-only-keys) has already been defined in docs-ref-autogen/latest/cosmosdb.pycliyml.
[Warning] Uid(az_cosmosdb_regenerate-key) has already been defined in docs-ref-autogen/latest/cosmosdb.pycliyml.
[Warning] Uid(az_cosmosdb_show) has already been defined in docs-ref-autogen/latest/cosmosdb.pycliyml.
[Warning] Uid(az_cosmosdb_update) has already been defined in docs-ref-autogen/latest/cosmosdb.pycliyml.

docs-ref-autogen/2017-03-09-profile/cosmosdb/collection.pycliyml

[Warning] Uid(az_cosmosdb_collection) has already been defined in docs-ref-autogen/latest/cosmosdb/collection.pycliyml.
[Warning] Uid(az_cosmosdb_collection_create) has already been defined in docs-ref-autogen/latest/cosmosdb/collection.pycliyml.
[Warning] Uid(az_cosmosdb_collection_delete) has already been defined in docs-ref-autogen/latest/cosmosdb/collection.pycliyml.
[Warning] Uid(az_cosmosdb_collection_exists) has already been defined in docs-ref-autogen/latest/cosmosdb/collection.pycliyml.
[Warning] Uid(az_cosmosdb_collection_list) has already been defined in docs-ref-autogen/latest/cosmosdb/collection.pycliyml.
[Warning] Uid(az_cosmosdb_collection_show) has already been defined in docs-ref-autogen/latest/cosmosdb/collection.pycliyml.
[Warning] Uid(az_cosmosdb_collection_update) has already been defined in docs-ref-autogen/latest/cosmosdb/collection.pycliyml.

docs-ref-autogen/2017-03-09-profile/dla.pycliyml

[Warning] Uid(az_dla) has already been defined in docs-ref-autogen/latest/dla.pycliyml.

docs-ref-autogen/2017-03-09-profile/dla/account/data-lake-store.pycliyml

[Warning] Uid(az_dla_account_data-lake-store) has already been defined in docs-ref-autogen/latest/dla/account/data-lake-store.pycliyml.
[Warning] Uid(az_dla_account_data-lake-store_add) has already been defined in docs-ref-autogen/latest/dla/account/data-lake-store.pycliyml.
[Warning] Uid(az_dla_account_data-lake-store_delete) has already been defined in docs-ref-autogen/latest/dla/account/data-lake-store.pycliyml.
[Warning] Uid(az_dla_account_data-lake-store_list) has already been defined in docs-ref-autogen/latest/dla/account/data-lake-store.pycliyml.
[Warning] Uid(az_dla_account_data-lake-store_show) has already been defined in docs-ref-autogen/latest/dla/account/data-lake-store.pycliyml.

docs-ref-autogen/2017-03-09-profile/dla/account/firewall.pycliyml

[Warning] Uid(az_dla_account_firewall) has already been defined in docs-ref-autogen/latest/dla/account/firewall.pycliyml.
[Warning] Uid(az_dla_account_firewall_create) has already been defined in docs-ref-autogen/latest/dla/account/firewall.pycliyml.
[Warning] Uid(az_dla_account_firewall_delete) has already been defined in docs-ref-autogen/latest/dla/account/firewall.pycliyml.
[Warning] Uid(az_dla_account_firewall_list) has already been defined in docs-ref-autogen/latest/dla/account/firewall.pycliyml.
[Warning] Uid(az_dla_account_firewall_show) has already been defined in docs-ref-autogen/latest/dla/account/firewall.pycliyml.
[Warning] Uid(az_dla_account_firewall_update) has already been defined in docs-ref-autogen/latest/dla/account/firewall.pycliyml.

docs-ref-autogen/2017-03-09-profile/dla/catalog.pycliyml

[Warning] Uid(az_dla_catalog) has already been defined in docs-ref-autogen/latest/dla/catalog.pycliyml.

docs-ref-autogen/2017-03-09-profile/dla/catalog/database.pycliyml

[Warning] Uid(az_dla_catalog_database) has already been defined in docs-ref-autogen/latest/dla/catalog/database.pycliyml.
[Warning] Uid(az_dla_catalog_database_list) has already been defined in docs-ref-autogen/latest/dla/catalog/database.pycliyml.
[Warning] Uid(az_dla_catalog_database_show) has already been defined in docs-ref-autogen/latest/dla/catalog/database.pycliyml.

docs-ref-autogen/2017-03-09-profile/dla/catalog/external-data-source.pycliyml

[Warning] Uid(az_dla_catalog_external-data-source) has already been defined in docs-ref-autogen/latest/dla/catalog/external-data-source.pycliyml.
[Warning] Uid(az_dla_catalog_external-data-source_list) has already been defined in docs-ref-autogen/latest/dla/catalog/external-data-source.pycliyml.
[Warning] Uid(az_dla_catalog_external-data-source_show) has already been defined in docs-ref-autogen/latest/dla/catalog/external-data-source.pycliyml.

docs-ref-autogen/2017-03-09-profile/dla/catalog/package.pycliyml

[Warning] Uid(az_dla_catalog_package) has already been defined in docs-ref-autogen/latest/dla/catalog/package.pycliyml.
[Warning] Uid(az_dla_catalog_package_list) has already been defined in docs-ref-autogen/latest/dla/catalog/package.pycliyml.
[Warning] Uid(az_dla_catalog_package_show) has already been defined in docs-ref-autogen/latest/dla/catalog/package.pycliyml.

docs-ref-autogen/2017-03-09-profile/dla/catalog/procedure.pycliyml

[Warning] Uid(az_dla_catalog_procedure) has already been defined in docs-ref-autogen/latest/dla/catalog/procedure.pycliyml.
[Warning] Uid(az_dla_catalog_procedure_list) has already been defined in docs-ref-autogen/latest/dla/catalog/procedure.pycliyml.
[Warning] Uid(az_dla_catalog_procedure_show) has already been defined in docs-ref-autogen/latest/dla/catalog/procedure.pycliyml.

docs-ref-autogen/2017-03-09-profile/dla/catalog/schema.pycliyml

[Warning] Uid(az_dla_catalog_schema) has already been defined in docs-ref-autogen/latest/dla/catalog/schema.pycliyml.
[Warning] Uid(az_dla_catalog_schema_list) has already been defined in docs-ref-autogen/latest/dla/catalog/schema.pycliyml.
[Warning] Uid(az_dla_catalog_schema_show) has already been defined in docs-ref-autogen/latest/dla/catalog/schema.pycliyml.

docs-ref-autogen/2017-03-09-profile/dla/catalog/table-partition.pycliyml

[Warning] Uid(az_dla_catalog_table-partition) has already been defined in docs-ref-autogen/latest/dla/catalog/table-partition.pycliyml.
[Warning] Uid(az_dla_catalog_table-partition_list) has already been defined in docs-ref-autogen/latest/dla/catalog/table-partition.pycliyml.
[Warning] Uid(az_dla_catalog_table-partition_show) has already been defined in docs-ref-autogen/latest/dla/catalog/table-partition.pycliyml.

docs-ref-autogen/2017-03-09-profile/dla/catalog/table-stats.pycliyml

[Warning] Uid(az_dla_catalog_table-stats) has already been defined in docs-ref-autogen/latest/dla/catalog/table-stats.pycliyml.
[Warning] Uid(az_dla_catalog_table-stats_list) has already been defined in docs-ref-autogen/latest/dla/catalog/table-stats.pycliyml.
[Warning] Uid(az_dla_catalog_table-stats_show) has already been defined in docs-ref-autogen/latest/dla/catalog/table-stats.pycliyml.

docs-ref-autogen/2017-03-09-profile/dla/catalog/table-type.pycliyml

[Warning] Uid(az_dla_catalog_table-type) has already been defined in docs-ref-autogen/latest/dla/catalog/table-type.pycliyml.
[Warning] Uid(az_dla_catalog_table-type_list) has already been defined in docs-ref-autogen/latest/dla/catalog/table-type.pycliyml.
[Warning] Uid(az_dla_catalog_table-type_show) has already been defined in docs-ref-autogen/latest/dla/catalog/table-type.pycliyml.

docs-ref-autogen/2017-03-09-profile/dla/job.pycliyml

[Warning] Uid(az_dla_job) has already been defined in docs-ref-autogen/latest/dla/job.pycliyml.
[Warning] Uid(az_dla_job_cancel) has already been defined in docs-ref-autogen/latest/dla/job.pycliyml.
[Warning] Uid(az_dla_job_list) has already been defined in docs-ref-autogen/latest/dla/job.pycliyml.
[Warning] Uid(az_dla_job_show) has already been defined in docs-ref-autogen/latest/dla/job.pycliyml.
[Warning] Uid(az_dla_job_submit) has already been defined in docs-ref-autogen/latest/dla/job.pycliyml.
[Warning] Uid(az_dla_job_wait) has already been defined in docs-ref-autogen/latest/dla/job.pycliyml.

docs-ref-autogen/2017-03-09-profile/dla/job/recurrence.pycliyml

[Warning] Uid(az_dla_job_recurrence) has already been defined in docs-ref-autogen/latest/dla/job/recurrence.pycliyml.
[Warning] Uid(az_dla_job_recurrence_list) has already been defined in docs-ref-autogen/latest/dla/job/recurrence.pycliyml.
[Warning] Uid(az_dla_job_recurrence_show) has already been defined in docs-ref-autogen/latest/dla/job/recurrence.pycliyml.

docs-ref-autogen/2017-03-09-profile/dls.pycliyml

[Warning] Uid(az_dls) has already been defined in docs-ref-autogen/latest/dls.pycliyml.

docs-ref-autogen/2017-03-09-profile/dls/account.pycliyml

[Warning] Uid(az_dls_account) has already been defined in docs-ref-autogen/latest/dls/account.pycliyml.
[Warning] Uid(az_dls_account_create) has already been defined in docs-ref-autogen/latest/dls/account.pycliyml.
[Warning] Uid(az_dls_account_delete) has already been defined in docs-ref-autogen/latest/dls/account.pycliyml.
[Warning] Uid(az_dls_account_enable-key-vault) has already been defined in docs-ref-autogen/latest/dls/account.pycliyml.
[Warning] Uid(az_dls_account_list) has already been defined in docs-ref-autogen/latest/dls/account.pycliyml.
[Warning] Uid(az_dls_account_show) has already been defined in docs-ref-autogen/latest/dls/account.pycliyml.
[Warning] Uid(az_dls_account_update) has already been defined in docs-ref-autogen/latest/dls/account.pycliyml.

docs-ref-autogen/2017-03-09-profile/dls/account/firewall.pycliyml

[Warning] Uid(az_dls_account_firewall) has already been defined in docs-ref-autogen/latest/dls/account/firewall.pycliyml.
[Warning] Uid(az_dls_account_firewall_create) has already been defined in docs-ref-autogen/latest/dls/account/firewall.pycliyml.
[Warning] Uid(az_dls_account_firewall_delete) has already been defined in docs-ref-autogen/latest/dls/account/firewall.pycliyml.
[Warning] Uid(az_dls_account_firewall_list) has already been defined in docs-ref-autogen/latest/dls/account/firewall.pycliyml.
[Warning] Uid(az_dls_account_firewall_show) has already been defined in docs-ref-autogen/latest/dls/account/firewall.pycliyml.
[Warning] Uid(az_dls_account_firewall_update) has already been defined in docs-ref-autogen/latest/dls/account/firewall.pycliyml.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

@georgechenchao should a reviewer be assigned to this or are you taking care of it?

Closing this as TOC changes have been merged from PR #451.

authors: formulahendry georgechenchao msftclas sptramer

repo: Azure/azure-docs-cli-python