text:
refactor: Move remaining code in pkg/tools/azcli/ to pkg/azapi

When we started azd instead of making REST calls against the Azure using the SDKs, we had an AzCli type which shelled out to az to preform work. Over time we refactored this code from using the exec package to run az to use the proper go SDKs from azure-sdk-for-go and as we did this we ended up pulling off related operations into their own services and packages.
Over time we got close to completely removing the AzCli type, but a few operations still lingered.
To finish the job while minimizing the destruction to the rest of the codebase, I've taken the AzCli type in pkg/tools/azcli/, moved all the code into pkg/azapi and then renamed the type from AzCli to AzureClient (following the azure-sdk-for-go convention of Client suffixes). While doing so, I removed the intermediate wrapper interface and now other components just take a *azapi.AzureClient instead of a azcli.AzCli.
Fixes #854

There were a handful of methods left of the old AzCli interface, and I considered breaking things down into a set of perhaps finer grained types as part of moving this code (instead of a more generic AzureClient as I did here) but I didn't see much of the benefit of doing so at this time.  I also keep the AzCli prefix on some of the exported types we have (even though the values don't come from the CLI anymore) again to just reduce the size of the diff.  I could imagine us removing these wrapper types at some point - they mostly existed so we could json.Unmarshal the output of az, which we don't do anymore - we could consider just exposing the types from the SDK directly.

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/4624/uninstall-azd.sh | bash;
curl -fsSL https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/4624/install-azd.sh | bash -s -- --base-url https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/4624 --version '' --verbose --skip-verify

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

Windows
PowerShell install
powershell -c "Set-ExecutionPolicy Bypass Process; irm 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/4624/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/4624/install-azd.ps1' > install-azd.ps1; ./install-azd.ps1 -BaseUrl 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/4624' -Version '' -SkipVerify -Verbose;"

MSI install
powershell -c "irm 'https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/4624/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/4624/azd-linux-amd64.tar.gz
ARM64 - https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/4624/azd-linux-arm64.tar.gz

MacOS -

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

Windows -

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

MSI

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

Documentation

learn.microsoft.com documentation

title: Azure Developer CLI reference
description: This article explains the syntax and parameters for the various Azure Developer CLI commands.
author: alexwolfmsft
ms.author: alexwolf
ms.date: 12/11/2024
ms.service: azure-dev-cli
ms.topic: conceptual
ms.custom: devx-track-azdevcli
Azure Developer CLI reference
This article explains the syntax and parameters for the various Azure Developer CLI commands.
azd
The Azure Developer CLI (azd) is an open-source tool that helps onboard and manage your application on Azure
Options
  -C, --cwd string   Sets the current working directory.
      --debug        Enables debugging and diagnostics logging.
      --docs         Opens the documentation for azd in your web browser.
  -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 add: Add a component to your project. (Alpha)
azd auth: Authenticate with Azure.
azd config: Manage azd configurations (ex: default Azure subscription, location).
azd deploy: Deploy the application's code to Azure.
azd down: Delete Azure resources for an application.
azd env: Manage environments.
azd hooks: Develop, test and run hooks for an application. (Beta)
azd infra: Manage your Azure infrastructure.
azd init: Initialize a new application.
azd monitor: Monitor a deployed application. (Beta)
azd package: Packages the application's code to be deployed to Azure. (Beta)
azd pipeline: Manage and configure your deployment pipelines. (Beta)
azd provision: Provision the Azure resources for an application.
azd restore: Restores the application's dependencies. (Beta)
azd show: Display information about your app and its resources.
azd template: Find and view template details. (Beta)
azd up: Provision Azure resources, and deploy your project with a single command.
azd version: Print the version number of Azure Developer CLI.

azd add
Add a component to your project. (Alpha)
azd add [flags]

Options
      --docs   Opens the documentation for azd add in your web browser.
  -h, --help   Gets help for add.

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 auth
Authenticate with Azure.
Options
      --docs   Opens the documentation for azd auth in your web browser.
  -h, --help   Gets help for auth.

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 auth login: Log in to Azure.
azd auth logout: Log out of Azure.
Back to top

azd auth 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, or --federated-credential-provider.
To log in using a managed identity, pass --managed-identity, which will use the system assigned managed identity.
To use a user assigned managed identity, pass --client-id in addition to --managed-identity with the client id of
the user assigned managed identity you wish to use.
azd auth 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.
      --docs                                   Opens the documentation for azd auth login in your web browser.
      --federated-credential-provider string   The provider to use to acquire a federated token to authenticate with.
  -h, --help                                   Gets help for login.
      --managed-identity                       Use a managed identity to authenticate.
      --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[=true]                 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

azd auth: Authenticate with Azure.
Back to top

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

Options
      --docs   Opens the documentation for azd auth logout in your web browser.
  -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

azd auth: Authenticate with Azure.
Back to top

azd config
Manage azd configurations (ex: default Azure subscription, location).
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
      --docs   Opens the documentation for azd config in your web browser.
  -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-alpha: Display the list of available features in alpha stage.
azd config reset: Resets configuration to default.
azd config set: Sets a configuration.
azd config show: Show all the configuration values.
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
      --docs   Opens the documentation for azd config get in your web browser.
  -h, --help   Gets help for get.

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 azd configurations (ex: default Azure subscription, location).
Back to top

azd config list-alpha
Display the list of available features in alpha stage.
azd config list-alpha [flags]

Options
      --docs   Opens the documentation for azd config list-alpha in your web browser.
  -h, --help   Gets help for list-alpha.

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 azd configurations (ex: default Azure subscription, location).
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
      --docs    Opens the documentation for azd config reset in your web browser.
  -f, --force   Force reset without confirmation.
  -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 azd configurations (ex: default Azure subscription, location).
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
      --docs   Opens the documentation for azd config set in your web browser.
  -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 azd configurations (ex: default Azure subscription, location).
Back to top

azd config show
Show all the configuration values.
Synopsis
Show 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 show [flags]

Options
      --docs   Opens the documentation for azd config show in your web browser.
  -h, --help   Gets help for show.

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 azd configurations (ex: default Azure subscription, location).
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
      --docs   Opens the documentation for azd config unset in your web browser.
  -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 azd configurations (ex: default Azure subscription, location).
Back to top

azd deploy
Deploy the application's code to Azure.
azd deploy <service> [flags]

Options
      --all                   Deploys all services that are listed in azure.yaml
      --docs                  Opens the documentation for azd deploy in your web browser.
  -e, --environment string    The name of the environment to use.
      --from-package string   Deploys the application from an existing package.
  -h, --help                  Gets help for deploy.

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 application.
azd down [flags]

Options
      --docs                 Opens the documentation for azd down in your web browser.
  -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.
      --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.
Options
      --docs   Opens the documentation for azd env in your web browser.
  -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-value: Get specific environment value.
azd env get-values: Get all environment values.
azd env list: List environments.
azd env new: Create a new environment and set it as the default.
azd env refresh: Refresh environment settings by using information from a previous infrastructure provision.
azd env select: Set the default environment.
azd env set: Manage your environment settings.
Back to top

azd env get-value
Get specific environment value.
azd env get-value <keyName> [flags]

Options
      --docs                 Opens the documentation for azd env get-value in your web browser.
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for get-value.

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 get-values
Get all environment values.
azd env get-values [flags]

Options
      --docs                 Opens the documentation for azd env get-values in your web browser.
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for get-values.

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
      --docs   Opens the documentation for azd env list in your web browser.
  -h, --help   Gets help for list.

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 and set it as the default.
azd env new <environment> [flags]

Options
      --docs                  Opens the documentation for azd env new in your web browser.
  -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 <environment> [flags]

Options
      --docs                 Opens the documentation for azd env refresh in your web browser.
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for refresh.
      --hint string          Hint to help identify the environment to refresh

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
      --docs   Opens the documentation for azd env select in your web browser.
  -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
Manage your environment settings.
azd env set <key> <value> [flags]

Options
      --docs                 Opens the documentation for azd env set in your web browser.
  -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 hooks
Develop, test and run hooks for an application. (Beta)
Options
      --docs   Opens the documentation for azd hooks in your web browser.
  -h, --help   Gets help for hooks.

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 hooks run: Runs the specified hook for the project and services
Back to top

azd hooks run
Runs the specified hook for the project and services
azd hooks run <name> [flags]

Options
      --docs                 Opens the documentation for azd hooks run in your web browser.
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for run.
      --platform string      Forces hooks to run for the specified platform.
      --service string       Only runs hooks for the specified service.

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 hooks: Develop, test and run hooks for an application. (Beta)
Back to top

azd infra
Manage your Azure infrastructure.
Options
      --docs   Opens the documentation for azd infra in your web browser.
  -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 synth: Write IaC for your project to disk, allowing you to manage it by hand. (Alpha)
Back to top

azd infra synth
Write IaC for your project to disk, allowing you to manage it by hand. (Alpha)
azd infra synth [flags]

Options
      --docs                 Opens the documentation for azd infra synth in your web browser.
  -e, --environment string   The name of the environment to use.
      --force                Overwrite any existing files without prompting
  -h, --help                 Gets help for synth.

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 your Azure infrastructure.
Back to top

azd init
Initialize a new application.
azd init [flags]

Options
  -b, --branch string         The template branch to initialize from. Must be used with a template argument (--template or -t).
      --docs                  Opens the documentation for azd init in your web browser.
  -e, --environment string    The name of the environment to use.
  -f, --filter strings        The tag(s) used to filter template results. Supports comma-separated values.
      --from-code             Initializes a new application from your existing code.
  -h, --help                  Gets help for init.
  -l, --location string       Azure location for the new environment
  -s, --subscription string   Name or ID of an Azure subscription to use for the new environment
  -t, --template string       Initializes a new application from a template. 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 monitor
Monitor a deployed application. (Beta)
azd monitor [flags]

Options
      --docs                 Opens the documentation for azd monitor in your web browser.
  -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 package
Packages the application's code to be deployed to Azure. (Beta)
azd package <service> [flags]

Options
      --all                  Packages all services that are listed in azure.yaml
      --docs                 Opens the documentation for azd package in your web browser.
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for package.
      --output-path string   File or folder path where the generated packages will be saved.

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 and configure your deployment pipelines. (Beta)
Options
      --docs   Opens the documentation for azd pipeline in your web browser.
  -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: Configure your deployment pipeline to connect securely to Azure. (Beta)
Back to top

azd pipeline config
Configure your deployment pipeline to connect securely to Azure. (Beta)
azd pipeline config [flags]

Options
  -m, --applicationServiceManagementReference string   Service Management Reference. References application or service contact information from a Service or Asset Management database. This value must be a Universally Unique Identifier (UUID). You can set this value globally by running azd config set pipeline.config.applicationServiceManagementReference <UUID>.
      --auth-type string                               The authentication type used between the pipeline provider and Azure for deployment (Only valid for GitHub provider). Valid values: federated, client-credentials.
      --docs                                           Opens the documentation for azd pipeline config in your web browser.
  -e, --environment string                             The name of the environment to use.
  -h, --help                                           Gets help for config.
      --principal-id string                            The client id of the service principal to use to grant access to Azure resources as part of the pipeline.
      --principal-name string                          The name of the service principal to use to grant access to Azure resources as part of the pipeline.
      --principal-role stringArray                     The roles to assign to the service principal. By default the service principal will be granted the Contributor and User Access Administrator roles. (default [Contributor,User Access Administrator])
      --provider string                                The pipeline provider to use (github for Github Actions and azdo for Azure Pipelines).
      --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 and configure your deployment pipelines. (Beta)
Back to top

azd provision
Provision the Azure resources for an application.
azd provision [flags]

Options
      --docs                 Opens the documentation for azd provision in your web browser.
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for provision.
      --no-state             Do not use latest Deployment State (bicep only).
      --preview              Preview changes to Azure resources.

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
Restores the application's dependencies. (Beta)
azd restore <service> [flags]

Options
      --all                  Restores all services that are listed in azure.yaml
      --docs                 Opens the documentation for azd restore in your web browser.
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for restore.

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 show
Display information about your app and its resources.
azd show [flags]

Options
      --docs                 Opens the documentation for azd show in your web browser.
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for show.
      --show-secrets         Unmask secrets in output.

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
Find and view template details. (Beta)
Options
      --docs   Opens the documentation for azd template in your web browser.
  -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: Show list of sample azd templates. (Beta)
azd template show: Show details for a given template. (Beta)
azd template source: View and manage template sources. (Beta)
Back to top

azd template list
Show list of sample azd templates. (Beta)
azd template list [flags]

Options
      --docs             Opens the documentation for azd template list in your web browser.
  -f, --filter strings   The tag(s) used to filter template results. Supports comma-separated values.
  -h, --help             Gets help for list.
  -s, --source string    Filters templates by source.

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: Find and view template details. (Beta)
Back to top

azd template show
Show details for a given template. (Beta)
azd template show <template> [flags]

Options
      --docs   Opens the documentation for azd template show in your web browser.
  -h, --help   Gets help for show.

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: Find and view template details. (Beta)
Back to top

azd template source
View and manage template sources. (Beta)
Options
      --docs   Opens the documentation for azd template source in your web browser.
  -h, --help   Gets help for source.

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: Find and view template details. (Beta)
azd template source add: Adds an azd template source with the specified key. (Beta)
azd template source list: Lists the configured azd template sources. (Beta)
azd template source remove: Removes the specified azd template source (Beta)
Back to top

azd template source add
Adds an azd template source with the specified key. (Beta)
Synopsis
The key can be any value that uniquely identifies the template source, with well-known values being:
・default: Default templates
・awesome-azd: Templates from https://aka.ms/awesome-azd
azd template source add <key> [flags]

Options
      --docs              Opens the documentation for azd template source add in your web browser.
  -h, --help              Gets help for add.
  -l, --location string   Location of the template source. Required when using type flag.
  -n, --name string       Display name of the template source.
  -t, --type string       Kind of the template source. Supported types are 'file', 'url' and 'gh'.

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 source: View and manage template sources. (Beta)
Back to top

azd template source list
Lists the configured azd template sources. (Beta)
azd template source list [flags]

Options
      --docs   Opens the documentation for azd template source list in your web browser.
  -h, --help   Gets help for list.

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 source: View and manage template sources. (Beta)
Back to top

azd template source remove
Removes the specified azd template source (Beta)
azd template source remove <key> [flags]

Options
      --docs   Opens the documentation for azd template source remove in your web browser.
  -h, --help   Gets help for remove.

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 source: View and manage template sources. (Beta)
Back to top

azd up
Provision Azure resources, and deploy your project with a single command.
azd up [flags]

Options
      --docs                 Opens the documentation for azd up in your web browser.
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for up.

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
      --docs   Opens the documentation for azd version in your web browser.
  -h, --help   Gets help for version.

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


text:
Updating DurableTask version from 2.3.0 to 2.3.1

Updated Microsoft.Azure.WebJobs.Extensions.DurableTask version from 2.3.0 to 2.3.1 in extensions.json.

Looks good to me! @soninaren, this version was just deployed, can we get your approval to merge?

/azp run

Hello @fabiocav -- Could you please force start the Azure.azure-functions-extension-bundles validation check? Thank you.

/azp run

The internal issue that was blocking this is now mitigated. Can we try rerunning the pipeline again?

/azp run

Hi @bachuv -- could you please squash your commits and merge the PR?

source: gharchive/pull-request

authors: ConnorMcMahon Francisco-Gamino bachuv davidmrdavid fabiocav yojagad

repo: Azure/azure-functions-extension-bundles

license: MIT

license_type: permissive

license_source: github-api


text:
Update RpcFunctionMetadata with more properties

Host needs RetryOptions and configuration source information to populate FunctionMetadata, so two more properties have been added to RpcFunctionMetadata to convey this information.
Some clarifying comments have also been added to RpcFunctionMetadata that specify what the attributes are supposed to contain.

Retry Options are addressed in PRs

https://github.com/Azure/azure-functions-language-worker-protobuf/commit/466445a6a9f887e20cc525fc24e23843e9bd5c47
https://github.com/Azure/azure-functions-host/pull/7134/files ,

for configuration source - I do not have a much context - @soninaren might


text:
Fix a docstring formatting typo

Missing trailing : for the url parameter causes the docstring to render improperly by including :param str url HTTP URL. in https://docs.microsoft.com/en-us/python/api/azure-functions/azure.functions.httprequest?view=azure-python and not listing url as a parameter.
Closes #19

@maiqbal11 can we merge this?

authors: asavaritayal brettcannon

repo: Azure/azure-functions-python-library


text:
MacOS python 3.* build

After I follow all the instructions I get an error:
Traceback (most recent call last):
File "app.py", line 4, in
from hub_client import send
File "/Users/shakedamar/Projects/axonize-python-sdk/hub_client.py", line 3, in
import iothub_client
ImportError: dynamic module does not define module export function (PyInit_iothub_client)
I tried with all the above versions: 3.5, 3.6, 3.7

@AmarShaked
Could you please send us the code you run?
Best Regards,
Zoltan

@AmarShaked
Please also send us the platform and SDK info. (OS and SDK version)
Best Regards,
Zoltan

Closing this out as it's been open for a bit.  @AmarShaked, if you can get us the code please re-activate this or else open a new issue.  Thanks.

@AmarShaked thank you for your contribution to our open-sourced project!  Please help us improve by filling out this 2-minute customer satisfaction survey.

source: gharchive/issue

authors: AmarShaked jspaith tameraw zolvarga

repo: Azure/azure-iot-sdk-python


text:
ASP.NET Core: NextLink is generated always (instead of when needed)

IN the List operation, the NextLink is always present.
Workaround (implemented): Only return NextLink if there is some data in the block.  This acts as a terminator for the request.
Todo:

[ ] Add a test for the paging operation to terminate
[ ] Re-add the code for NextLink once we work out what the appropriate code is
[ ] Re-test.

Was fixed when #83 was implemented

repo: Azure/azure-mobile-apps

license: mit

license_source: bigquery


text:
Make sure all projects are updated to target API 21

Per the meeting on content freshness, we want to make sure we target the newest Android API in every release. Quickstart is targeting 19 (is there a reason for this?), and I haven't looked into other files. But we want to make sure everything targets the latest ver unless an older ver is justified. @soninaren @marianosz

didn't realize there can only be one assignee. I meant for us to all keep track of this and we want everything to be updated before GA.

Closed with PR #561

authors: aziel ysxu

repo: Azure/azure-mobile-services


text:
[DO NOT MERGE] Initial commit to add workload management apis to synapse RP

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of “no breaking changes
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[x] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

Please follow the link to find more details on PR review process.

/azp run automation - sdk

Hi @tunafish88 , some api path doesn't have the MIME type definition.  It would be good to add them to root level instead of api path level if they're same.
"consumes": [
    "application/json"
  ],
  "produces": [
    "application/json"
  ]`

/azp run automation - sdk

/azp run automation - sdk

Hi @tunafish88 , some api path doesn't have the MIME type definition. It would be good to add them to root level instead of api path level if they're same.
"consumes": [
    "application/json"
  ],
  "produces": [
    "application/json"
  ]`

Thanks. This helped

/azp run automation - sdk

/azp run automation - sdk

Hi @tunafish88 this PR now looks good to me.
Since this PR still needs ARM's feedback, I will hold my approval to avoid any accidentally merging. I will approve and merge this once ARM signs off on this PR.
Thanks

/azp run automation - sdk

/azp run automation - sdk

Hi @tunafish88 could you please also update the examples to fix the ModelValidation check?

Closing this pull request because after making ARM recommended changes to treat some strings representing hh:mm to format 'date-time' , the API behavior is broken. The API only accepts string , and takes 'hh:mm'. For now, since we do not need this swagger urgently, I'll be closing this PR and we don't need the check in right now. We will discuss with the internal team and send out a new PR if needed.

repo: Azure/azure-rest-api-specs


text:
Add missing properties for api version 2020-02-02-preview of securityAlertPolicies

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[x] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No, no need to refresh for updates in this PR

Contribution checklist:

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[ ] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from Breaking Change Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable or public preview version with Breaking Change Validation errors
[ ] Updating API(s) in public preview over 1 year (refer to Retirement of Previews)

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

please fix the validation errors triggered by your example files in the DSMainDev repo firstly. Then you can update in this github PR.

and also let me know why add new properties in a existing version. it is required a new API version if it is adding a new feature,

@ericshape - I fixed the errors in DsmMainDev
@akning-ms - I am doing this change becuase of many CRIs we got for this API version. These properties don't apply a new behavior. They exist in the previous versions of these APIs (2017-03-01-preview for servers and managed instances and 2018-06-01-preview for databases). We tried to remove these settings, but got a lot of CRIs of customers complaining on this change, therefore we want to return the properties that exist in the previous versions. Moreover, this API was published less than one year ago, and since it is a preview version we can add these properites. please approve this change

@ericshape - I fixed the errors in DsmMainDev
@akning-ms - I am doing this change becuase of many CRIs we got for this API version. These properties don't apply a new behavior. They exist in the previous versions of these APIs (2017-03-01-preview for servers and managed instances and 2018-06-01-preview for databases). We tried to remove these settings, but got a lot of CRIs of customers complaining on this change, therefore we want to return the properties that exist in the previous versions. Moreover, this API was published less than one year ago, and since it is a preview version we can add these properites. please approve this change

Thanks, few more questions, Can I know  the PR#  which removed these properties?  and CRIs of customer complaining is from SDK?  BTW, you may need to remove the package-lock.json in this PR.

@ericshape - I fixed the errors in DsmMainDev
@akning-ms - I am doing this change becuase of many CRIs we got for this API version. These properties don't apply a new behavior. They exist in the previous versions of these APIs (2017-03-01-preview for servers and managed instances and 2018-06-01-preview for databases). We tried to remove these settings, but got a lot of CRIs of customers complaining on this change, therefore we want to return the properties that exist in the previous versions. Moreover, this API was published less than one year ago, and since it is a preview version we can add these properites. please approve this change

Thanks, few more questions, Can I know the PR# which removed these properties? and CRIs of customer complaining is from SDK? BTW, you may need to remove the package-lock.json in this PR.

@ayeletshpigelman I have replied to the comments in your DSMain PR and tag @akning-ms in the comment as well.

@ericshape - I added the changes to version 2020-11-01-preview and version 2020-08-01-preview as well
@akning-ms - The pr of removing these settings in the new version is: https://github.com/Azure/azure-rest-api-specs/pull/9565
CRIS for example: https://portal.microsofticm.com/imp/v3/incidents/details/217576651/home
I also sent you over email 2 other examples

LGTM

the breaking changes are expected. it seems because @ayeletshpigelman would like to add these features to V5 SDK. The version of v5 SDK I will merge is based on 2020-08-01 preview.
lintDiff throws an exception. I think it is fine in that the exception is systemData. cc: @akning-ms
.NET sdk test is failed due to @xaliciayang has not updated the test in .NET repo. It is expected.

@jianyexi to check why there is exception for Linter, this error can not be skipped, as it stops the linter validation

@jianyexi Jianye Xi FTE to check why there is exception for Linter, this error can not be skipped, as it stops the linter validation

The  systemData is referenced by https://github.com/Azure/azure-rest-api-specs/blob/26a8083f016be439122fe390dacd27a5b7ef2649/specification/sql/resource-manager/Microsoft.Sql/preview/2020-11-01-preview/ServerDevOpsAudit.json#L225  , but is conflict with the systemData at  :
https://github.com/Azure/azure-rest-api-specs/blob/master/specification/common-types/resource-management/v1/types.json#L441
please use the latter one

@jianyexi - I don't under the explanation. ServerDevOpsAudit.json is not owned by me. In my files I used the following ref: "$ref": "../../../../../common-types/resource-management/v1/types.json#/definitions/systemData"
which leads to the file you suggested to use.
If there is a problem with ServerDevOpsAudit.json please fix this, but it is not related to my changes.
@akning-ms - Appreciate your approval, we got another CRI regarding this during the weekend. Customers are waiting for the fix
thank you

@jianyexi - I fixed the lint diff
@akning-ms - Appreciate your approval, we got another CRI regarding this during the weekend. Customers are waiting for the fix
thank you

@ayeletshpigelman  @jianyexi
please use the SQL specific systemData: https://github.com/Azure/azure-rest-api-specs/blob/47b422a4d1ea9f4736739a4a6a19d4a8a2fe54d9/specification/sql/resource-manager/common/v1/types.json#L100

the systemData filed in all SQL DB APIs is a dummy. we did not impl it. I think Jenny has let all the ARM reviewers know it.
the SQL DB specific common file is different from the global common one. We have a lot of specific enum values which global one does not support.

authors: akning-ms ayeletshpigelman ericshape jianyexi


text:
[Hub Generated] Publish private branch 'datafactory/v-jinpan/Script'

This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
ARM API Information (Control Plane)
Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo.  If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.

The PR is created based on the updates in the private branch. The updates in the PR has already been reviewed and approved with this PR Azure/azure-rest-api-specs-pr/9177


text:
[Hub Generated] Review request for Microsoft.CostManagement to add version 2019-03-01-preview

Main changes:

Field changes related to CloudConnector,ExternalBillingAccount,ExternalSubscription
Remove API POST: /providers/Microsoft.Management/managementGroups/{managementGroupId}/providers/Microsoft.CostManagement/getEntities
Add API PUT:
/providers/Microsoft.Management/managementGroups/{managementGroupId}/providers/Microsoft.CostManagement/externalSubscriptions
Reformat costmanagement.json with VisualStudio Code
Fix typo Managment -> Management

Details of Field changes:

CloudConnector: renamed providerAccountId to providerBillingAccountId
CloudConnector: added providerBillingAccountDisplayName, externalBillingAccountId
CloudConnector: changed status to be readonly (no longer part of PUT)
CloudConnector: changed PATCH to not take a connector properties, and therefore to be used only for verifying an existing cloudconnector
ExternalBillingAccount: added providerBillingAccountId, connectorId
ExternalBillingAccount: added GET $expand=collectionInfo
ExternalSubscription: added providerBillingAccountId, providerAccountId
ExternalSubscription: added GET $expand=collectionInfo

If you are a MSFT employee you can view your work branch via this link.
Contribution checklist:

[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.

Automation for azure-sdk-for-js

Automation for azure-sdk-for-python

Automation for azure-sdk-for-node

Automation for azure-sdk-for-ruby

Can one of the admins verify this patch?

Automation for azure-sdk-for-go

@AutorestCI regenerate azure-sdk-for-go

Automation for azure-sdk-for-java

@AutorestCI regenerate azure-sdk-for-go

@sergey-shandar Can you look into the issue with the Defrault build issue?
https://azuresdkci.westus2.cloudapp.azure.com/job/DotNetSwaggerToSdkCI/73/

startbuild

startbuild

@praries880 ignore failures on "default" job.
We recently renamed the job to "Automation for azure-sdk-for-net"

Arieh, There are lot of breaking changes and must be done in new api version.

    "operationId": "CloudConnector_Verify",

why renaming a patch operation as '_verify' , instead of '_update' ?

Refers to: specification/cost-management/resource-manager/Microsoft.CostManagement/preview/2019-03-01-preview/costmanagement.json:1326 in ef9b6d3. [](commit_id = ef9b6d3914b85107a9d26a999f30f44c3564395f, deletion_comment = False)

Automation for azure-sdk-for-net
A PR has been created for you:
https://github.com/azure/azure-sdk-for-net/pull/-1
.NET SDK Commits:
https://github.com/adxsdknet/azure-sdk-for-net/pull/-1/commits/

    "operationId": "CloudConnector_Verify",

why renaming a patch operation as '_verify' , instead of '_update' ?
Refers to: specification/cost-management/resource-manager/Microsoft.CostManagement/preview/2019-03-01-preview/costmanagement.json:1326 in ef9b6d3. [](commit_id = ef9b6d3, deletion_comment = False)

Renamed _verify to _update

Automation for azure-sdk-for-net
A PR has been created for you:
https://github.com/azure/azure-sdk-for-net/pull/-1
.NET SDK Commits:
https://github.com/adxsdknet/azure-sdk-for-net/pull/-1/commits/

@sanjaiganesh / @antmarti-microsoft Can you validate that the latest commits handle the ARM feeback?

Automation for azure-sdk-for-net
A PR has been created for you:
https://github.com/azure/azure-sdk-for-net/pull/-1
.NET SDK Commits:
https://github.com/adxsdknet/azure-sdk-for-net/pull/-1/commits/

authors: AutorestCI adxsdknet ariehf azuresdkci dsgouda praries880 sanjaiganesh shahabhijeet


text:
Top Level WAF Swagger Changes

Link To Previous PR:
https://github.com/Azure/azure-rest-api-specs/pull/6851
Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

Automation for azure-sdk-for-python

Can one of the admins verify this patch?

Automation for azure-sdk-for-go

@number213  I have done the same. Please check.

@majastrz please review this from ARM's side

@majastrz this is a branch for new API version that's not merged into master yet. Could you please approve this PR if there are no other concerns?

@zikalino could you please review and merge?

Per call with @venkatsvpr there may be some changes so adding "do not merge" tag for now

@tjprescott assigning this to you since Catherine Zhu said you're one of those who would cover for Chinese team during their long holiday. Could you please merge this PR?

authors: AutorestCI azuresdkci number213 venkatsvpr


text:
Need to validate and check failure condition on open call

This is not a goal of this PR, I am just moving things around, let's take care of this in a separate PR. @vhvb1989 will you look into this, should be a simple fix, or should I create a work item?
Originally posted by @antkmsft in https://github.com/Azure/azure-sdk-for-cpp/pull/1070#discussion_r535527294

duplicated from https://github.com/Azure/azure-sdk-for-cpp/issues/1074

repo: Azure/azure-sdk-for-cpp


text:
The TumblingWindowTrigger struct is missing the Annotations field

Bug Report

services/datafactory/mgmt/2018-06-01/datafactory/models.go
23.0.0
go version go1.11.4 linux/amd64

What happened?
The TumblingWindowTrigger struct is missing the Annotations field.
What did you expect or want to happen?
To set the Annotations field.
How can we reproduce it?
Try setting the Annotations field.
Anything we should know about your environment.
The API accepts the field, and the DF UI sets and uses it. If I manually add it, it works just fine.

Ported to https://github.com/Azure/azure-rest-api-specs/issues/5274

authors: jhendrixMSFT kung-foo

repo: Azure/azure-sdk-for-go


text:
[Release] sdk/resourcemanager/devcenter/armdevcenter/0.3.0

https://github.com/Azure/sdk-release-request/issues/3302

@Alancere Please help to confirm the breaking changes. Could they be resolved by remove unreferenced types?

The struct OperationStatusError was referenced in the previous version

authors: Alancere azure-sdk tadelesh


text:
[AutoPR automation/resource-manager] Add x-ms-parameter-location property

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/3404

This PR has been merged into https://github.com/Azure/azure-sdk-for-go/pull/2220


text:
Fix links to docs site

This PR updates any links in the github repo to the documentation site since old links may now 404. This PR is against the master branch since that is where godoc builds from, and it appears that the docs.go file is not contained in latest.

[X] The purpose of this PR is explained in this or a referenced issue.
[X] The PR does not update generated files.

These files are managed by the codegen framework at Azure/autorest.go.

[ ] The PR targets the latest branch.
[ ] Tests are included and/or updated for code changes.
[ ] Updates to CHANGELOG.md are included.
[ ] Apache v2 license headers are included in each file.

Can one of the admins verify this patch?

Hi @sptramer , could you please re-target this pr to latest branch?
Therefore this update will be online on next minor version release, latest on next major release at end of this month.

@ArcturusZhang The docs.go file is not present in the latest branch, which is why master was targeted. This is the only file that needs to be updated, and is only really used by godoc builds, which always target master (if I understand correctly.)

authors: ArcturusZhang azuresdkci sptramer


text:
Fix azure-cosmos changelog

Fix azure-cosmos changelog
https://github.com/Azure/azure-sdk-for-java/blob/master/sdk/cosmos/azure-cosmos/CHANGELOG.md

This is done.

repo: Azure/azure-sdk-for-java


text:
Run security checks on internal pipeline

We would like to periodically run security checks to identify vulnerabilities reported for any of the dependencies used in Java SDK. I manually ran the maven command below to identify a couple of libraries that were reported. One of them had a newer version that fixed it and the other was a false positive. So, for now, we have no known issues but we’d like to automate this process. is it possible to have this run in an internal pipeline daily and flag issues? Please let me know if you need additional details.
Maven command:
mvn dependency-check:check -f pom.client.xml
Maven plugin:
<plugin>
  <groupId>org.owasp</groupId>
  <artifactId>dependency-check-maven</artifactId>
  <version>5.2.2</version>
  <executions>
       <execution>
             <goals>
                  <goal>check</goal>
             </goals>
       </execution>
  </executions>
</plugin>

Pick this one up from Jim.

There is a nightly run which performs this task for the entirety of the repository now.

authors: alzimmermsft mitchdenny srnagar


text:
[FEATURE REQ] PollerFlux will always do the polling loop

Describe the bug
For PollerFlux, the activationOperation will return Mono<T>, but not Mono<PollResponse<T>>.
And in some ARM long-running operation cases, it will directly return 200 during the first REST calling. However, in currently implementation, the code will do the polling loop anyway which is delay with some default interval. We should support this scenario.
        this.oneTimeActivationMono
            .flatMapMany(ignored -> pollingLoop())
            .subscribe(actual);

PR with this feature is merged, hence closing.

authors: anuchandy yaohaizh


text:
Fix error in image about aad resource-server.

Fix error in image about aad resource-server.

Hi, @backwind1233 , @zhichengliu12581 , @yiliuTo .
Please help to review this PR.

LGTM


text:
removed UUI

Description
Please add an informative description that covers that changes made by the pull request and link all relevant issues.
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

API change check
APIView has identified API level changes in this PR and created following API reviews.
azure-communication-callautomation

authors: azure-sdk juntuchen-msft


text:
Update known issues in azure-identity-extensions

Description
Add some known issues and troubleshooting guides.
All SDK Contribution checklist:

[X] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

API change check
API changes are not detected in this pull request.


text:
Sync .github/workflows directory with azure-sdk-tools for PR 6440

Sync .github/workflows directory with azure-sdk-tools for PR https://github.com/Azure/azure-sdk-tools/pull/6440  See eng/common workflow

Overriding check-enforcer. There's no pipeline that'll run that'll test these changes.

/check-enforcer override

authors: JimSuplizio azure-sdk


text:
Split live test runs by service

The current list of reviewers is probably not complete...

Use templates to reduce duplications
Scope variables to relevant projects

For the following projects with live tests:

applicationconfig
batch
eventhubs
keyvault
servicebus
storage

Once this is merged we'll need to create integration testing pipelines

@Azure/azure-sdk-eng

@mitchdenny do you think it would be best to way until we move the projects before enabling these pipelines? If not it will require that we update all the pipelines as well as the file paths in the yml files after the move.

Feel free to merge this now. As I go through and do the restructuring I can add this to the clean-up activities on each one.

As the repo directory structure changes land we'll have to do two things:

Update the tests.yml files to point to the correct archetype yml path
Update pipelines to point at the new location for the tests.yml files that have moved

authors: danieljurek mitchdenny weshaggard


text:
[Automation] Generate Fluent Lite from datafactory#package-2018-06

[Automation] Generate Fluent Lite from datafactory#package-2018-06

/azp run java - datafactory - mgmt - tests


text:
Add From Source run to Cosmos CI

Description
Adds a From Source run to Cosmos CI.
All SDK Contribution checklist:

[ ] The pull request does not introduce [breaking changes]
[ ] CHANGELOG is updated for new features, bug fixes or other significant changes.
[ ] I have read the contribution guidelines.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

/azp run java - cosmos - ci

/azp run java - cosmos

@FabianMeiswinkel, mind taking a look at this PR


text:
[Automation] Generate Fluent Lite from Swagger maps#package-2023-06

[Automation] Generate Fluent Lite from Swagger maps#package-2023-06

API change check
APIView has identified API level changes in this PR and created following API reviews.
com.azure.resourcemanager:azure-resourcemanager-maps


text:
Increment versions for servicelinker releases

Increment package versions for servicelinker releases

API change check
API changes are not detected in this pull request.


text:
[Service Bus] Incorrect package owners on npmjs.com

Going forward, all Azure SDK packages on npmjs.com should have the azure-sdk account as the single owner.  The first version of the @azure/service-bus package was published using the azure-sdk credentials from an Azure DevOps Release Pipeline, so we expected azure-sdk to be the only owner.  However, somehow my personal account mikeharder is also listed as an owner:
$ npm owner ls @azure/service-bus
mikeharder <mharder@microsoft.com>
azure-sdk <azuresdkengsysadmins@microsoft.com>

Attempting to remove owner mikeharder generates error about an undefined team.  It's unclear how removing an owner is related to a "team".
$ npm owner rm mikeharder @azure/service-bus
npm ERR! owner mutate Failed to update package metadata
npm ERR! code E404
npm ERR! 404 Team not found : undefined
npm ERR! 404
npm ERR! 404  'undefined' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.

We don't understand the root cause of either behavior, but we speculate it might be related to the configuration of the @azure org in npmjs.com.
CC: @bterlson

Hi @mikeharder, since you opened the ticket a while ago I don't know if you're still having the trouble, but perhaps there are others that will also stumble upon this ticket that can get some help out of it.
I was getting the same issue and what I ended up doing is using the npm website to fix it, if you log in to an admin user's account and go to account settings, click on the org on the left, then go to teams and select "Packages" for the team the user that needs their access revoked belongs to, you can remove it there.

@chiel: Thanks for the suggestion, I will try this and update the issue with the results.

@chiel: It worked!  Thank you so much.

authors: chiel mikeharder

repo: Azure/azure-sdk-for-js


text:
Get NetworkInterface Details API  with api version 2020-04-01 failure

Package Name: "@azure/arm-network"
Package Version: "21.1.0"
Operating system:
[ ] nodejs

13.13.0

Describe the bug
GET https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/networkInterfaces/{networkInterfaceName}?api-version=2020-04-01  returns
{
"error": {
"code": "NoRegisteredProviderFound",
"message": "No registered resource provider found for location 'eastus' and API version '2020-04-01' for type 'networkInterfaces'. The supported api-versions are '2014-12-01-preview, 2015-05-01-preview, 2015-06-15, 2016-03-30, 2016-06-01, 2016-07-01, 2016-08-01, 2016-09-01, 2016-10-01, 2016-11-01, 2016-12-01, 2017-03-01, 2017-04-01, 2017-06-01, 2017-08-01, 2017-09-01, 2017-10-01, 2017-11-01, 2018-01-01, 2018-02-01, 2018-03-01, 2018-04-01, 2018-05-01, 2018-06-01, 2018-07-01, 2018-08-01, 2018-10-01, 2018-11-01, 2018-12-01, 2019-02-01, 2019-04-01, 2019-06-01, 2019-07-01, 2019-08-01, 2019-09-01, 2019-11-01, 2019-12-01, 2020-01-01, 2020-03-01'. The supported locations are 'westus, eastus, northeurope, westeurope, eastasia, southeastasia, northcentralus, southcentralus, centralus, eastus2, japaneast, japanwest, brazilsouth, australiaeast, australiasoutheast, centralindia, southindia, westindia, canadacentral, canadaeast, westcentralus, westus2, ukwest, uksouth, koreacentral, koreasouth, francecentral, southafricanorth, uaenorth, australiacentral, australiacentral2'."
}
}
This API was working until 3rd June 2020.
To Reproduce
GET https://management.azure.com/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/Microsoft.Network/networkInterfaces/{networkInterfaceName}?api-version=2020-04-0
Expected behavior
return network interface details
Additional context
The API works with api-version=2020-03-01

@qiaozha, Can you add the right label here to route it to the right team?

Add service attention tag. why this new API version swagger https://github.com/Azure/azure-rest-api-specs/pull/9282 is merged  and asked for SDK release if the service backend is not ready?

Just been told that this is because server end problem the new api verson has been add back. @ntapsrigowri  Can you try again to see if the problem is still there? thx

i just verified it at my end too. It works , thank you !

Close this one as resolved

authors: ntapsrigowri qiaozha ramya-rao-a


text:
[KeyVault] - Enable multi-version tests for KV admin

What

Add support for multi-version testing for keyvault-admin

Why
Our commitment is to support the last N versions of the KeyVault service. To ensure neither we nor the service introduce breaking changes to prior versions, multi-version test support was added. We ported keys over and have already reaped the benefits of version based filtering.
This commit adds the same support for keyvault-admin
Resolves #19791

/azp run js - keyvault-admin - tests

/azp run js - keyvault-admin - tests

/azp run js - keyvault-admin - tests

/azp run js - keyvault-admin - tests

Test failures due to #19754 and are not related to this PR. The fix has not been rolled out yet by the service so feel free to override and merge 👍

authors: maorleger sadasant


text:
Update OpenTelemetry code snippets in Azure Monitor Exporter readme

Fixes #20672

/azp run js - monitor - ci

/azp run js - monitor - ci

API changes have been detected in @azure/monitor-opentelemetry-exporter. You can review API changes here
API changes
+     aadTokenCredential?: TokenCredential;

authors: azure-sdk hectorhdzg praveenkuttappan


text:
Post release automated changes for databricks releases

Post release automated changes for azure-arm-databricks

API change check
API changes are not detected in this pull request.


text:
live tests use resource allocator templates and scripts in eng/common/TestResources

Use a static variable to get around the fact that the service matrices mostly differ from each other. This makes sense if we define properties like OSVmImage, TestType and NodeVersion in the matrix and then set other properties based on those types of tests (the way that we do in the matrix template expansion)

/azp run js - appconfiguration - tests

/azp run js - keyvault-secrets - tests


text:
Unpin dev dependency "follow-redirects"

follow-redirects@1.12.1 removes peer dependency "debug"
Fixes #9612

/azp run js - storage-blob - tests


text:
[core-autorest] Create package for AutoRest specific code

In order to do #8615, I'm creating a new package where we can put all AutoRest-specific code that is intended to help codegen map payloads to/from Swagger-specified schemas.
There's no real code in this initial PR, it's just the template scaffolding so we don't have to review it in the next PR when there's actual code to examine. 😉

@joheredi this is the package you can feel free to put any codegen helpers into! ❤

Just a high level comment on naming: I think @azure/core-autorest might be confusing for people who are searching for other AutoRest-related things on npm; I think it'd be better to name it something like core-serviceclient, core-genutils, or something to that effect.  Neither of those two names are perfect so other suggestions would be helpful!

Just a high level comment on naming: I think @azure/core-autorest might be confusing for people who are searching for other AutoRest-related things on npm; I think it'd be better to name it something like core-serviceclient, core-genutils, or something to that effect. Neither of those two names are perfect so other suggestions would be helpful!

So the concern is that @azure/core-autorest would be more appealing of a name than either autorest or @autorest/autorest when folks are looking for AutoRest?
I guess I'm not sure how to name something that is exclusively for dealing with AutoRest but that doesn't name AutoRest explicitly. I don't think we should bake ServiceClient into the name, as that might go away some day.
Would @azure/core-autorest-adapter be better in your view, @daviwil?

It's not that it's more appealing, it's that there's a few similarly-named packages on npm:

autorest
@autorest/autorest (yeah)
@autorest/core

What does the module actually do?  It's not that it "does AutoRest things", it's a library used by generated SDK clients.  When the rubber meets the road, this library facilitates serialization of SDK-level REST operations using generated model and operation types.  The fact that AutoRest generated the code that uses this library isn't really relevant at the time it gets used, in my opinion.
All that said, I don't hold this opinion very strongly so do what ye will :)

Renamed this to core-client for now, unless someone has a more dashing name.

authors: daviwil xirzec


text:
Add ReceiptTypeConfidence field to USReceipt

ReceiptType comes back as a field in DocumentResults, without a bounding box, but with a confidence value.  Add a float? ReceiptTypeConfidence to USReceipt to capture the confidence.

Consider adding FormEnumField type per APIView discussion below:

public USReceiptType ReceiptType { get; }
...annelo-msft1 day ago As @samvaity also pointed out, we will need to add a field to indicate the confidence in the ReceiptType prediction.
bojunehsu1 day agoCan't we use FormField then?
...annelo-msft15 hours agoThat would also have a Name, Label, text value and strongly-typed value. It seems like more than we would want for this field, since it doesn't have a physical representation in the receipt.
bojunehsu8 hours agoSemi tempted to introduce FormEnumField with T Value and float Confidence.

FYI: @bojunehsu

If we add FormEnumField type, we would do it in Preview 2.  Creating separate issue #11237 to track this.  This would be a good thing to bring up in the arch board review to get their perspective on it.

repo: Azure/azure-sdk-for-net


text:
Design how to surface relationships in TA

Relations are present in Opinion Mining, healthcare, and possible other endpoints.
It will be ideal if across the SDK we manage this relationships the same way.
See https://github.com/Azure/azure-sdk-for-net/issues/15809 for more information

Service version 2.1-preview.4 will bring a N-N graph. Moving this to next milestone when the SDK will target that release

Design proposal can be found here => https://apiview.dev/Assemblies/Review/329cfc783b474d97891a5349e705feb4?diffRevisionId=94926e8ff2954c6b8da109e47e5cc417&doc=False&diffOnly=False

We decided to leave relations exposed as is, and according to feedback we will implement convenience methods


text:
Expose locale parameter in method as an extensible enum instead of string

Needs to be per endpoint? looks like it

Because service team is currently exposing Locale and Language as generic to their service, I will follow the same in .NET.
There are plans in the future to have a consolidated method for all prebuilts and having specific enums per prebuilt model will not work

Because service team is currently exposing Locale and Language as generic to their service, I will follow the same in .NET.
There are plans in the future to have a consolidated method for all prebuilts and having specific enums per prebuilt model will not work


text:
[FEATURE REQ] Missing extension for AppConfiguration

Azure.Data.AppConfiguration.
Azure.Extensions.AspNetCore.Configuration.Secrets makes it easy to add Azure KeyVault into the configuration builder during startup. I have not found any similar for Azure.Data.AppConfiguration.
There is a Microsoft.Extensions.Configuration.AzureAppConfiguration for the “old” Microsoft.Azure.AppConfiguration.AspNetCore (actually updated today).
Are there any plans add this? Just for fun I took the code in Azure.Extensions.AspNetCore.Configuration.Secrets and adapted it to AppConfiguration instead. Not that hard, I think. I could create an PR if there is an interest.

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

Libraries that you've mentioned are not "old", they are current, supported, and based on Azure.Data.AppConfiguraiton.
Microsoft.Extensions.Configuration.AzureAppConfiguration is a IConfiguration-AppConfig extension package.
Microsoft.Azure.AppConfiguration.AspNetCore has a few additional features on top of that mostly around refreshing configuration during the request processing.
I would recommend starting with Microsoft.Extensions.Configuration.AzureAppConfiguration.

authors: jsquire pakrym pekspro


text:
[BUG] AppendBlobClient.CreateIfNotExistsAsync() logging 409 (Conflict) BlobAlreadyExists in Storage Diagnostics

Library name and version
Azure.Storage.Blobs 12.14.1
Describe the bug
Using AppendBlobClient.CreateIfNotExistsAsync() is logging 409 (Conflict) BlobAlreadyExists in storage diagnostics on AppendBlock operation.
Expected behavior
I would expect the method to only log a transaction when the blob is first created and not produce a BlobAlreadyExists on every append.
Actual behavior
409 (Conflict) BlobAlreadyExists logged on every AppendBlock operation.
Reproduction Steps
`
var numberOfApppends = 100;
var counter = 0;
var blobName = "blob_test/test_1.json";
while (counter < numberOfApppends)
{
Console.WriteLine($"Appnding {counter}...");

var blobServiceClient = new BlobServiceClient(storageConnectionString);

var containerClient = blobServiceClient.GetBlobContainerClient("bronze");
AppendBlobClient appendBlobClient = containerClient.GetAppendBlobClient(blobName);

if( !await appendBlobClient.ExistsAsync() )
{

    Console.WriteLine($"Creating blob: {blobName}");
    await appendBlobClient.CreateIfNotExistsAsync();

}

string json = "{\"Key\": \"" + counter.ToString() + "\"}";
byte[] blockContent = Encoding.ASCII.GetBytes(json);

using var ms = new MemoryStream(blockContent);

await appendBlobClient.AppendBlockAsync(ms);

counter++;

}
`
Environment
Azure Function .NET 6 version ~4

Hm looks like this was just missed when this PR was done.
https://github.com/Azure/azure-sdk-for-net/pull/33639
Marking as a bug for now as we attempt to make a solution.
Thanks for bringing this up to our attention.

Hello,
any update on this issue ?

Do we just use exists and create instead until this is resolved?

authors: amnguye benwilkinson lymedo pthorey


text:
Flaky build: attribute 'EventProcessorClient' that could not be resolved

Some builds fail with the following error:
BlobPartitionManager.cs(283,91): error CS1574: XML comment has cref attribute 'EventProcessorClient' that could not be resolved [D:\a\1\SourceDirWith49CharsLengthTestForLongPaths\sdk\eventhub\Azure.Messaging.EventHubs.CheckpointStore.Blobs\src\Azure.Messaging.EventHubs.CheckpointStore.Blobs.csproj]

Restart makes the failure go away.
Example: https://dev.azure.com/azure-sdk/public/_build/results?buildId=177551&view=logs&j=96d7b680-dcef-5cfd-cab1-6c247ea8b6c3&t=6fa7484a-d027-52bc-0b8f-217fe61fafa9&l=162
cc @weshaggard @danieljurek @chidozieononiwu @jsquire

This now fails a lot more: https://dev.azure.com/azure-sdk/public/_build/results?buildId=177647&view=logs&j=1e00682f-6081-5348-8da2-7d601664b2e3

Context:  This type was renamed in the latest release; this appears to be a transient (but sometimes difficult to clear) exception related to resolving the NuGet package dependency for Event Hubs 5.0.0-preview.5; this issue began after moving to a package reference (from project reference) this morning.

I believe I have fixed this by overwriting some invalid packages on our blob feed with the versions we GA'ed this week. I'm going to close this issue now but please do re-open if you see any other similar failures.

authors: jsquire pakrym weshaggard


text:
[Webjobs Service bus SDK] Added auto-complete feature at the function level

Porting over auto-complete messages feature add the function level

@alrod, FYI for this change..

This is in regard to https://github.com/Azure/azure-functions-servicebus-extension/pull/155 PR originally created for Track 1 SDK.

you'll need to regenerate the API by running .\Export-API.ps1 servicebus from the eng\scripts directory

authors: JoshLove-msft apranaseth


text:
Migrate samples for HybridData and Kubernetes

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

API change check
API changes are not detected in this pull request.

authors: azure-sdk dvbb


text:
[BingVisualSearch] Additional query parameters: mkt, safesearch, setlang

Description
Additional query parameters for the Visual Search API allowing users to specify market, safesearch level, and language for the results.  REST spec PR link.

This checklist is used to make sure that common guidelines for a pull request are followed.

[x] Please add REST spec PR link to the SDK PR
[x] I have read the contribution guidelines.
[x] The pull request does not introduce breaking changes.

General Guidelines

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[x] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[x] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.
[x] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

Please link the related REST spec PR

@dsgouda oh! sorry, i had it linked in the checklist but forgot to add it to the description. it's there now :)

authors: dsgouda shakao


text:
Support new Azure Compute API "SimulateEviction" for both Standalone VM and VMSS VM via Python SDK

Is your feature request related to a problem? Please describe.
We released new API "SimulateEviction" in Azure Compute. We want Python SDK support for it. There are two APIs with the same API name. One for Standalone VM and another for VMScaleSet VM.
https://docs.microsoft.com/en-us/rest/api/compute/virtualmachines/simulateeviction
https://docs.microsoft.com/en-us/rest/api/compute/virtualmachinescalesetvms/simulateeviction
Describe the solution you'd like
Supporting this Compute API via Python SDK
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Swagger Links
https://github.com/Azure/azure-rest-api-specs/pull/8929
https://github.com/Azure/azure-rest-api-specs/pull/9102
Additional context
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[x] Description Added
[x] Expected solution specified

Thanks @sandeepkv93, @nickzhums could you take a look at this

@RodgeFu please help have a look

@sandeepkv93 please request release of the new package via: https://portal.azure-devex-tools.com/tools/request-api-release

@zikalino Sure, created a request

https://github.com/Azure/sdk-release-request/issues/382 has been created to track the request release, so close this one. thanks.

authors: RodgeFu kaerm nickzhums sandeepkv93 zikalino

repo: Azure/azure-sdk-for-python


text:
[ServiceBus] Message body allows dictionary but can't receive the message

azure-servicebus:
7.0.0b6:
Windows:
3.7.9:

Describe the bug
According to the docs azure.servicebus.Message can accept string or bytes as body but by mistake I sent a dictionary without converting to string or bytes, the message was sent but I was not able to receive message on the other end. I spent a lot of time thinking my code was wrong on the other side cause I see there is a message active in the service bus.
Later I realized the error is because I sent the body without converting to string or bytes. Is there a way we could check for the type when creating the message?
To Reproduce
Following is example code which resulted in message getting stuck in the servicebus.
dict_test = {
"test1": "",
"test2": {
"test3": "",
"test4": "",
"test5":"westus2",
"test6": "2020-09-24"
},
}
message = Message(dict_test)
Expected behavior
Should not allow message body to be other type than string or bytes

Hey @divyag9 ;
Thanks for reaching out!  This is more perfect timing that you probably know, as we were contemplating this failure mode internally, and you've given strong impetus to taking action on it.
I believe were're in agreement as to the semantic goal, that invalid types should fail-fast with a ValueError during Message construction; the subtlety that we've been debating has been how to do this validation in a robust and complete way, as the breakdown of valid types is a little more fine-grained then mentioned.  (e.g. there are some valid AMQP scenarios involving lists, although the behavior is sometimes unintuitive)
Will keep this thread looped in as we settle on a conclusion and PR it in, expect to see something in this release cycle, and don't hesitate to shout here if you have any thoughts on the above or additional color to add.

Great thank you!

Hey @divyag9 , just wanted to close this out with the good news that the 7.0 GA release contains the expected fail-fast behavior in Message construction.
There is ongoing work in accordance to python guidelines to support Valid dict-representations in leiu of strongly typed arguments (see here ) but this should not distract from the behavior when an invalid dict is passed, to immediately raise a TypeError.
Don't hesitate to shout/reopen if any further questions or issues, and thanks as always for reaching out and your patience as we addressed this!


text:
azure.mgmt.web.models.SkuDescription: required field metadata and documentation are missing

When I omit name from the call to begin_create_or_update on an AppServicePlan, I get an error of InvalidRequestContent indicating the property is required.  None of the other properties appear to be required - if the name is a valid "size" then the server accepts the content.
The metadata for SkuDescription has no _validation so none of the fields appear to be marked as required.
When I provide the name by itself, things work:
Request:
(Pdb) pp uut.proposed.sku.as_dict()
{'name': 'B1'}

Response:
(Pdb) pp uut.real.sku.as_dict()
{'capacity': 1, 'family': 'B', 'name': 'B1', 'size': 'B1', 'tier': 'Basic'}

Additionally, it looks like the fields other than name are actually readonly, but not marked as such, for example see the request below which should be confusing to the server, but is not because it ignores size and tier in the request:
Request:
(Pdb) pp uut.proposed.sku.as_dict()
{'name': 'B1', 'size': 'F1', 'tier': 'Premium'}

Response:
(Pdb) pp uut.real.sku.as_dict()
{'capacity': 1, 'family': 'B', 'name': 'B1', 'size': 'B1', 'tier': 'Basic'}

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 714d22c2-e0bf-0514-0c79-2df33620ac31
Version Independent ID: fc440021-8305-be7c-0537-e315041e599a
Content: azure.mgmt.web.v2019_08_01.models.SkuDescription class
Content Source: docs-ref-autogen/azure-mgmt-web/azure.mgmt.web.v2019_08_01.models.SkuDescription.yml
GitHub Login: @lmazuel
Microsoft Alias: lmazuel

Same issue: https://github.com/Azure-Samples/azure-samples-python-management/issues/59

Same issue: https://github.com/Azure-Samples/azure-samples-python-management/issues/59


text:
Release Event Hubs for Python 2020 Feb Milestone

Post GA enhancements

@YijunXieMS Please move the pending issues to #9795 and close this issue.
For anyone else reading this,
There is no update planned for Event Hubs in Feb 2020

authors: YijunXieMS ramya-rao-a


text:
Remove OSName Variable

Remove OSName since it is being set here

/azp run python - eventhub - ci

/azp run python - eventhub - ci

Test failures are unrelated so merging to unblock the OSName issue.

authors: chidozieononiwu weshaggard


text:
[Dpg] DPG integration

https://github.com/Azure/azure-sdk-tools/issues/3420
test link: https://github.com/Azure/azure-sdk-for-python/pull/25398

/check-enforcer override


text:
[AutoRelease] t2-cosmosdb-2022-07-29-98207(Do not merge)

https://github.com/Azure/sdk-release-request/issues/3052
Live test success
https://dev.azure.com/azure-sdk/internal/_build?definitionId=984
BuildTargetingString
azure-mgmt-cosmosdb
Skip.CreateApiReview
true

issue link:https://github.com/Azure/sdk-release-request/issues/3052


text:
[AutoPR hdinsight/resource-manager] [HDInsight] Change accessModes and applicationType from enum to string

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/6785

(message created by the CI based on PR content)

This PR has been merged into https://github.com/Azure/azure-sdk-for-python/pull/6082