text:
Bad LINQ to SQL translation for filter on non-nullable boolean property

(already reported in v2, problem is still here in v3)
Describe the bug
LINQ queries with a condition on a non-nullable boolean property are not correctly translated to SQL. The translation doesn't account for the fact that the property could be undefined in the JSON document.
To Reproduce
Assuming an object model like this:
public class Item
{
    [JsonProperty("id")]
    public string Id { get; set; }

    public bool IsDeleted { get; set; }
}

Make the following query:
var query = container.GetItemLinqQueryable<Item>().Where(i => !i.IsDeleted);

Expected behavior
Documents where IsDeleted is not defined should be returned, because in the C# model the property is not nullable, so its absence really means that it's false.
The generated SQL should be something like this:
SELECT * FROM root WHERE (NOT IS_DEFINED(root["IsDeleted"]) OR NOT root["IsDeleted"])

Or maybe
SELECT * FROM root WHERE (NOT (root["IsDeleted"] ?? false))

Actual behavior
Documents where IsDeleted is not defined are not returned, because NOT (undefined) doesn't evaluate to true.
The generated SQL looks like this:
SELECT * FROM root WHERE (NOT root["IsDeleted"])

Environment summary
SDK Version: .NET Core 2.1, Microsoft.Azure.Cosmos 3.1.1
OS Version (e.g. Windows, Linux, MacOSX): Windows 10

I would argue this behaving correctly. If you look at the ECMA standards null is not equal to false. Here is a related stackoverflow  question.
c# the closes thing to undefined is null. A nullable bool that is null is not equal to false.
bool? test = null;
if(test == false){
  Console.Writeline("This will not be hit.");
}else{
 Console.Writeline("null is not equal to false");
}

What you are looking for is here.
var query = container.GetItemLinqQueryable<Item>().Where(i => !i.IsDeleted || !i.IsDefined());

Hi @j82w,
I agree that undefined isn't equal to false, however in this scenario, the query is driven by the C# model, where the IsDeleted property is not nullable. On deserialization, the property will be set to false. So for all intents and purposes, the property being undefined in the JSON document is equivalent to it being false in the C# model.
I'm aware of the IsDefined() trick, but I shouldn't have to do that in this situation. Having to use IsDefined() means that the abstraction (querying a C# object model) is leaking the fact that the property could in fact be undefined in the JSON document.

Hi @thomaslevesque ,
That's a good point. @kirankumarkolli what is your opinion?

Hi @j82w,
I agree that undefined isn't equal to false, however in this scenario, the query is driven by the C# model, where the IsDeleted property is not nullable. On deserialization, the property will be set to false. So for all intents and purposes, the property being undefined in the JSON document is equivalent to it being false in the C# model.
I'm aware of the IsDefined() trick, but I shouldn't have to do that in this situation. Having to use IsDefined() means that the abstraction (querying a C# object model) is leaking the fact that the property could in fact be undefined in the JSON document.

I agree.  We're running into this in our design too.  We abstract out the Cosmos stuff but still need to educate devs and remind ourselves that "It might look like C#, but it's actually JSON so use .IsDefined()".
But I'm opinionated just because of the path we chose.
So even though I agree, I kinda would be worried about special-casing this.  Because what if there's two types of C# documents you're storing?  One has your IsDeleted field, and the other doesn't.
container
    .GetItemLinqQueryable<IDictionary<string, object>>()
    .Where(x=>!(bool)x["IsDeleted"])
    .ToQueryDefinition()
    .QueryText;

>> SELECT VALUE root FROM root WHERE (NOT root["IsDeleted"])

If I'm using a Type field as a discriminator to know what to deserialize, I might be intending to filter out anything that doesn't have that field.
Further, what if it's an int instead?  The default value in C# is zero.  But what if I want to filter for when there's actually a zero in the document?

I agree that undefined isn't equal to false, however in this scenario, the query is driven by the C# model, where the IsDeleted property is not nullable. On deserialization, the property will be set to false. So for all intents and purposes, the property being undefined in the JSON document is equivalent to it being false in the C# model.

Isn't default-value after desalinization is also implementation dependent (ex: default value, default constructor).

The data and the data model don't match in this case (if the C# model is used to create data then we should only have boolean values for the property). It seems there're multiple versions of data (before and after IsDeleted is introduced). That means the scenario to filter on only the data set which has IsDeleted set to false is valid.
Translating !IsDeleted to both false equality and undefined assumes these two are equivalent (or implementation depended as Kiran mentioned above).
Consider the scenario where we have a property call IsNotDeleted, which has an opposite value of the IsDeleted property. Should we include undefined when filtering on IsNotDeleted? it depends on the scenario's definition of the undefined. So undefined can't seem to be implied with filtering on a boolean property.

For the case where data model changes like in this issue, it seems there're a few options:

option 1: use with a model that can include changes (if we can foresee)
option 2: update all the data to match with the new model value
option 3: adjust the query to account for previous and current data model

Because what if there's two types of C# documents you're storing? One has your IsDeleted field, and the other doesn't.

It depends on which type you're querying with. If the type has a non-nullable IsDeleted field, and the query includes something like !x.IsDeleted, translate to NOT (root["IsDeleted"] ?? false). If the type is a dictionary, as in your example, don't make any assumption and translate the query to NOT root["IsDeleted"].

If I'm using a Type field as a discriminator to know what to deserialize, I might be intending to filter out anything that doesn't have that field.

But in this case, shouldn't you filter on the Type field? Relying on the presence or absence of a field in the document seems brittle.

Further, what if it's an int instead? The default value in C# is zero. But what if I want to filter for when there's actually a zero in the document?

I don't think that's a very common scenario. If the property is not nullable in the C# model, you don't expect the field to be missing in the document ; and if it is missing, the value would be set to 0 in the C# object on deserialization anyway. If you really need to filter documents that do have an explicit value, you can always do it in SQL.

Isn't default-value after desalinization is also implementation dependent (ex: default value, default constructor).

Yes, but it doesn't really matter, I think. What matters here is the semantics of the model type you're using in the query. If a property is not nullable in the C# model, you shouldn't have to worry about whether it's present in the document or not.

The data and the data model don't match in this case (if the C# model is used to create data then we should only have boolean values for the property). It seems there're multiple versions of data (before and after IsDeleted is introduced). That means the scenario to filter on only the data set which has IsDeleted set to false is valid.

Indeed, it's a case where the IsDeleted property was introduced later.

Translating !IsDeleted to both false equality and undefined assumes these two are equivalent (or implementation depended as Kiran mentioned above).
Consider the scenario where we have a property called IsNotDeleted, which has an opposite value of the IsDeleted property. Should we include undefined when filtering on IsNotDeleted = true? it depends on the scenario's definition of the undefined. So undefined can't seem to be implied with a particular value of the boolean property.

That's a fair point. I didn't think about that. But maybe it could be handled with a [DefaultValue] attribute? If the property is not nullable, assume the default value (possibly specified with the [DefaultValue] attribute) when the property is missing in the document?
I realize it all seems unnecessarily complex, but the scenario I described is probably quite common, and having to specify || !x.IsDeleted.IsDefined() in the query isn't intuitive at all and is likely to cause a lot of bugs.

So in this case because the data and the model doesn't match, the specific behavior has to be specified. If we opt for a specific default behavior, it could lead to a different kind of confusion as in my previous comments.
Currently, we can set this behavior by adding the condition || !x.IsDeleted.IsDefined() as you mentioned. I think [DefaultValue] is an option we can consider. However, from a user point of view, he would also need to be aware of the need to specify the null-value behavior, in which case I would argue that it's comparably intuitive to add the not IsDefined(..) check.
We've taken note of this and will consider it for future change. I'm closing this issue for now.

I have a related problem but this time with a nullable field. Hope it's ok to share a link to SO: https://stackoverflow.com/questions/70062891/cosmos-db-iqueryable-on-nullable-fields

authors: azzimuth j82w joshlang khdang kirankumarkolli thomaslevesque


text:
Deploy Aspire Project from different Branches within the same project. Infrastructure provision step failing

I am using azd version 1.11.0 to deploy Aspire Project using below mentioned link
https://learn.microsoft.com/en-us/dotnet/aspire/deployment/azure/aca-deployment-github-actions?tabs=windows&pivots=azure-pipelines
Issue :
Project is already created and initiated using azd init, my current branch is dev.

using this command azd pipeline config --provider azdo
service connection is created automatically
PAT is configured with required permissions.

First deployment from let us say Branch dev works fine and deployment started.
Second deployment from let us say Branch Stagging but different container app envoironment using azd init using the same PAT  created in previous step and Azure service connection ( az connection) fails with error .
AZURE_ENV_NAME is invalid.

@vhvb1989 can you triage it?

Hello @faisalriazz , can you please add more details about what you are doing?  What do you mean by second deployment?
How are you trying to use different branches in your Azure DevOps?
When you run azd pipeline config, azd takes care of setting the CI/CD pipeline based on your current local git branch.  Any other branches are not configured, only the one you are currently using.  Azd sets ENV VARS for the pipeline that it creates.
Also, the documentation from https://learn.microsoft.com/en-us/dotnet/aspire/deployment/azure/aca-deployment-github-actions?tabs=windows&pivots=azure-pipelines is a little outdated.  You don't need to manually create the pipeline definition. You can just run azd pipeline config and azd will create it for you if it is missing.

@vhvb1989 Thanks for your reply. Here are the details that i have done so far.

In Branch main-cicd which i have created from main branch.
I just run azd pipeline config and follow the procedure.
Pipeline is working fine.

Now i repeated the same process but this time the Branch is main.

Pipeline executed sucessfully.
Issue is that both pipelines are trigerred for any change in one the branches either main or main-cicd.
I have updated the triggers in azure-dev.yml file in both branches as

main-cicd branch
trigger:
  branches:
    include:
      - main-cicd
    exclude:
      - main

main branch
trigger:
  branches:
    include:
      - main
    exclude:
      - main-cicd

** Still both pipelines are triggered on change in any of the branch**

I override the YML triggers in pipeline setting with the same as written in YML file.
Now invidiual pipelines are trigerred but this is not understandable.
Note I tried changing the name of the azure-dev.yml file in one branch and executed the pipeline but it failed in infrastructure provisioning task.
Ultimately i have to revert the filename back to azure-dev.yml

@rajeshkamal5050 @vhvb1989
Would you please update

@v-xuto can you repro the above steps and update? cc @vhvb1989

@faisalriazz , thank you for the details.
Every time you run azd pipeline config, azd creates a definition for the pipeline and the branch you are currently using.  The pipeline is the same, however.  Azd currently does not support handling more than one pipeline for you.
I remember we built it this way to prevent creating a new pipeline after every azd pipeline config.  Instead, we check if the pipeline already exist and update its definition.  This is causing you an issue b/c you are re-running with a different branch.
I'll see if we can include the branch name while we check if the pipeline exists or not.  In that case, you should see a different pipeline created for each branch.
Since this might take me some time, please be patient :)

Thanks @vhvb1989 for the update, will be waiting anxiously for new version of azd :)

@rajeshkamal5050, According to the steps, we cannot create two separate pipelines. Moreover, within the same pipeline, when we make changes and push to the main and main-cicd branches, only the corresponding branch's azure-dev.yml file will be executed.

@v-weiyding Thanks for your input. Yes that can done but i want to keep it separate pipelines for the sake of simplicity.
I will be waiting for update azd version.

source: gharchive/issue

repo: Azure/azure-dev

license: MIT

license_type: permissive

license_source: github-api


text:
fix install kubectl

fix: https://github.com/Azure/azure-dev/issues/3471
using instructions from: https://kubernetes.io/docs/tasks/tools/install-kubectl-linux/#install-using-native-package-management

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

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

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

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

MacOS -

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

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

MSI

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

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

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: 03/05/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 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 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 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.
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.
      --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-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-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 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.
  -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       The template to use when you initialize the project. You can use Full URI, <owner>/<repository>, or <repository> if it's part of the azure-samples organization.

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

See also

Back to top

azd 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
      --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.

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.
  -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 at 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 at the specified key (Beta)
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.
  -n, --name string       Display name of the template source.
  -t, --type string       Kind of the template 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 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

Closed in favor of #3474

source: gharchive/pull-request

authors: azure-sdk vhvb1989 wbreza


text:
console: Handle default value associated with OptionDetails

Handle default value associated with OptionDetails so that they would match correctly.
Fixes #3786

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

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

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

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

MacOS -

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

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

MSI

https://azuresdkreleasepreview.blob.core.windows.net/azd/standalone/pr/3788/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: 04/24/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 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 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 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.
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.
      --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-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-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 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.
      --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
      --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.

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.
  -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 at 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 at the specified key (Beta)
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.
  -n, --name string       Display name of the template source.
  -t, --type string       Kind of the template 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 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

authors: azure-sdk weikanglim


text:
AttributeError in worker.py when running function locally

Investigative information
I am following the documentation https://docs.microsoft.com/en-us/azure/azure-functions/functions-create-first-function-python?toc=%2Fpython%2Fazure%2FTOC.json to create an azure function in python. Everything goes smoothly and breaks when I execute "func host start".

I am not sure if this is a dependency issue or not, any help is appreciated.

@tinaj2505 what version of the Core Tools are you using?

@asavaritayal I tried it both on "2.2.103" and  "2.4.317" but  got same issue.

Can you try choco uninstall azure-functions-core-tools and then choco install azure-functions-core-tools? Not likely, but might be due to some inconsistent state during installation. If choco installations do not work, you can also try npm install -g azure-functions-core-tools after uninstalling the choco version. Feel free to circle back with the results if these steps don't work.

Interesting, now it's working when I reboot my computer after uninstall/install azure core tools in choco. Thank you!

repo: Azure/azure-functions-python-worker


text:
The local source 'D:\a\1\s\local-packages' doesn't exist.

Build step fails with the below error:

It's been 3 weeks with the above fix and we have not seen this error, closing this, we can reopen if we hit it again.

repo: Azure/azure-functions-sql-extension


text:
Telemetry window closes when events come in.

Describe the bug
When viewing telemetry for a device, the telemetry view closes when an event arrives.  This works fine in 0.10.14.
To Reproduce
Steps to reproduce the behavior:

Search for and select device.
Click on 'Telemetry'
Click on 'Start'
When event comes in, the right hand side of the window closes.

Expected behavior
A display stream of events is shown.
Screenshots

Desktop (please complete the following information):

OS: Mac
OS Version: 10.15.4
App version 0.10.15 and 0.10.16 (works in 0.10.14)

hi @damiandiaz76 please avoid use this feature at this point. The event hub sdk had the entity path/event hub name specified as optional paratemeter, but after digging a bit more, it is required in order to retreive events.
We will need to add another input for users to input this piece of info before we can enable this feature.
Sorry for the incovenience.

https://github.com/Azure/azure-iot-explorer/releases/tag/v0.10.18
Latest release has been published to address this issue.
Closing.

I still see this issue on Version 0.10.18 (0.10.18.20200506.1).

@damiandiaz76 Were you able to input both event hub connection string and event hub?

Yes
It happens with a custom event hub and with the built in endpoint.
Yes

It appears to me that the connection gets established. Have you tried running the "Telemetry" screen, clicked "Start" and then sent a telemetry message from the connected device?  Once the message comes in, that's when I see the screen close.

@damiandiaz76
Yes, and I am able to see it fine. Some steps that may help here.

Click help -> toggle developer tools, and check if the network tab has made an api call 'monitor'.

Check if the highlighted parameters are present
Check if you are seeing the response

If both of them shows correctly, check if there is vertial scroll bar somewhere on the app, maybe some unexpected response has messed up with the style and push the right side of the app down.

The connection parameters are present.
I do see the response come in.
I can't find any scroll bars in the app.

Here's an example response I'm getting with several messages.  Some of the properties have escaped json strings intentionally:
[{"body":{"version":1162,"properties":{"reported":{"host":"1ef13bef0036","pip":"73.78.223.139","$metadata":{"$lastUpdated":"2020-05-11T21:59:41.6704399Z","host":{"$lastUpdated":"2020-05-11T21:59:41.6704399Z"},"pip":{"$lastUpdated":"2020-05-11T21:59:41.6704399Z"}},"$version":63}}},"enqueuedTime":"2020-05-11T21:59:41.922Z","properties":{"hubName":"ddiaz-iot-iothub-westus2","deviceId":"sampledevice","operationTimestamp":"2020-05-11T21:59:41.6704399+00:00","iothub-message-schema":"twinChangeNotification","opType":"updateTwin","siteUUID":"$twin.tags.siteUUID","deviceinit":"$twin.tags.deviceinit","networkinfo":"{"data":{"802.1xStatus":"false","cdpStatus":"NA","connectionMode":"half-duplex","connectionSpeed":"1000Mbps","connectionType":"eth0","dnsAlternativeAddress":"","dnsDomain":"polycom.com","dnsPrimaryAddress":"10.223.10.1","eapMethod":"PEAP","ipv4Address":"10.223.75.46","ipv4AddressSource":"manual","ipv4Gateway":"10.223.75.253","ipv4Subnet":"255.255.255.0","ipv4Vlan":"1","ipv6AddressSource":"NA","ipv6GlobalAddress":"NA","ipv6LinkLocalAddress":"NA","ipv6ULA":"NA","lldpLocationInformation":"NA","lldpNeighbors":"NA","lldpStatus":"active","ntpServer":"Auto","pcPortStatus":"NA","provisioningProtocol":"HTTPS"},"rto":"15","type":"ni"}","roomUUID":"fs","primarydeviceinfo":"{"data":{"hardwareModel":"nodejs","hardwareRevision":"7","macAddress":"00:aa:bb:cc:dd:ee","manufacturer":"Polycom","offsetGMT":"-06:00","productFamily":"G7500","serialNumber":"sampledevice","softwareBuild":"212128","softwareRelease":"3.0.1"},"rto":"15","type":"pdi"}","tenantUUID":"t","devicepip":"73.78.223.139","devicemetadata":"{"deviceName":"Mo PolyOS 3.1.1"}"}},{"body":{"name":"UPLOAD_INLINE","type":"request","frameId":"frameId","payload":{"data":{"hardwareModel":"nodejs","hardwareRevision":"7","macAddress":"00:aa:bb:cc:dd:ee","manufacturer":"Polycom","offsetGMT":"-06:00","productFamily":"G7500","serialNumber":"sampledevice","softwareBuild":"212128","softwareRelease":"3.0.1"},"rto":"15","type":"pdi"}},"enqueuedTime":"2020-05-11T21:59:42.141Z","properties":{"siteUUID":"$twin.tags.siteUUID","deviceinit":"$twin.tags.deviceinit","networkinfo":"{"data":{"802.1xStatus":"false","cdpStatus":"NA","connectionMode":"half-duplex","connectionSpeed":"1000Mbps","connectionType":"eth0","dnsAlternativeAddress":"","dnsDomain":"polycom.com","dnsPrimaryAddress":"10.223.10.1","eapMethod":"PEAP","ipv4Address":"10.223.75.46","ipv4AddressSource":"manual","ipv4Gateway":"10.223.75.253","ipv4Subnet":"255.255.255.0","ipv4Vlan":"1","ipv6AddressSource":"NA","ipv6GlobalAddress":"NA","ipv6LinkLocalAddress":"NA","ipv6ULA":"NA","lldpLocationInformation":"NA","lldpNeighbors":"NA","lldpStatus":"active","ntpServer":"Auto","pcPortStatus":"NA","provisioningProtocol":"HTTPS"},"rto":"15","type":"ni"}","roomUUID":"fs","primarydeviceinfo":"{"data":{"hardwareModel":"nodejs","hardwareRevision":"7","macAddress":"00:aa:bb:cc:dd:ee","manufacturer":"Polycom","offsetGMT":"-06:00","productFamily":"G7500","serialNumber":"sampledevice","softwareBuild":"212128","softwareRelease":"3.0.1"},"rto":"15","type":"pdi"}","tenantUUID":"t","devicepip":"73.78.223.139","devicemetadata":"{"deviceName":"Mo PolyOS 3.1.1"}"}},{"body":{"name":"UPLOAD_INLINE","type":"request","frameId":"frameId","payload":{"data":{"802.1xStatus":"false","cdpStatus":"NA","connectionMode":"half-duplex","connectionSpeed":"1000Mbps","connectionType":"eth0","dnsAlternativeAddress":"","dnsDomain":"polycom.com","dnsPrimaryAddress":"10.223.10.1","eapMethod":"PEAP","ipv4Address":"10.223.75.46","ipv4AddressSource":"manual","ipv4Gateway":"10.223.75.253","ipv4Subnet":"255.255.255.0","ipv4Vlan":"1","ipv6AddressSource":"NA","ipv6GlobalAddress":"NA","ipv6LinkLocalAddress":"NA","ipv6ULA":"NA","lldpLocationInformation":"NA","lldpNeighbors":"NA","lldpStatus":"active","ntpServer":"Auto","pcPortStatus":"NA","provisioningProtocol":"HTTPS"},"rto":"15","type":"ni"}},"enqueuedTime":"2020-05-11T21:59:42.141Z","properties":{"siteUUID":"$twin.tags.siteUUID","deviceinit":"$twin.tags.deviceinit","networkinfo":"{"data":{"802.1xStatus":"false","cdpStatus":"NA","connectionMode":"half-duplex","connectionSpeed":"1000Mbps","connectionType":"eth0","dnsAlternativeAddress":"","dnsDomain":"polycom.com","dnsPrimaryAddress":"10.223.10.1","eapMethod":"PEAP","ipv4Address":"10.223.75.46","ipv4AddressSource":"manual","ipv4Gateway":"10.223.75.253","ipv4Subnet":"255.255.255.0","ipv4Vlan":"1","ipv6AddressSource":"NA","ipv6GlobalAddress":"NA","ipv6LinkLocalAddress":"NA","ipv6ULA":"NA","lldpLocationInformation":"NA","lldpNeighbors":"NA","lldpStatus":"active","ntpServer":"Auto","pcPortStatus":"NA","provisioningProtocol":"HTTPS"},"rto":"15","type":"ni"}","roomUUID":"fs","primarydeviceinfo":"{"data":{"hardwareModel":"nodejs","hardwareRevision":"7","macAddress":"00:aa:bb:cc:dd:ee","manufacturer":"Polycom","offsetGMT":"-06:00","productFamily":"G7500","serialNumber":"sampledevice","softwareBuild":"212128","softwareRelease":"3.0.1"},"rto":"15","type":"pdi"}","tenantUUID":"t","devicepip":"73.78.223.139","devicemetadata":"{"deviceName":"Mo PolyOS 3.1.1"}"}},{"body":{"version":1163,"tags":{"primarydeviceinfo":"{"data":{"hardwareModel":"nodejs","hardwareRevision":"7","macAddress":"00:aa:bb:cc:dd:ee","manufacturer":"Polycom","offsetGMT":"-06:00","productFamily":"G7500","serialNumber":"sampledevice","softwareBuild":"212128","softwareRelease":"3.0.1"},"rto":"15","type":"pdi"}"}},"enqueuedTime":"2020-05-11T21:59:42.344Z","properties":{"hubName":"ddiaz-iot-iothub-westus2","deviceId":"sampledevice","operationTimestamp":"2020-05-11T21:59:42.1820355Z","iothub-message-schema":"twinChangeNotification","opType":"updateTwin","siteUUID":"$twin.tags.siteUUID","deviceinit":"$twin.tags.deviceinit","networkinfo":"{"data":{"802.1xStatus":"false","cdpStatus":"NA","connectionMode":"half-duplex","connectionSpeed":"1000Mbps","connectionType":"eth0","dnsAlternativeAddress":"","dnsDomain":"polycom.com","dnsPrimaryAddress":"10.223.10.1","eapMethod":"PEAP","ipv4Address":"10.223.75.46","ipv4AddressSource":"manual","ipv4Gateway":"10.223.75.253","ipv4Subnet":"255.255.255.0","ipv4Vlan":"1","ipv6AddressSource":"NA","ipv6GlobalAddress":"NA","ipv6LinkLocalAddress":"NA","ipv6ULA":"NA","lldpLocationInformation":"NA","lldpNeighbors":"NA","lldpStatus":"active","ntpServer":"Auto","pcPortStatus":"NA","provisioningProtocol":"HTTPS"},"rto":"15","type":"ni"}","roomUUID":"fs","primarydeviceinfo":"{"data":{"hardwareModel":"nodejs","hardwareRevision":"7","macAddress":"00:aa:bb:cc:dd:ee","manufacturer":"Polycom","offsetGMT":"-06:00","productFamily":"G7500","serialNumber":"sampledevice","softwareBuild":"212128","softwareRelease":"3.0.1"},"rto":"15","type":"pdi"}","tenantUUID":"t","devicepip":"73.78.223.139","devicemetadata":"{"deviceName":"Mo PolyOS 3.1.1"}"}},{"body":{"version":1164,"tags":{"networkinfo":"{"data":{"802.1xStatus":"false","cdpStatus":"NA","connectionMode":"half-duplex","connectionSpeed":"1000Mbps","connectionType":"eth0","dnsAlternativeAddress":"","dnsDomain":"polycom.com","dnsPrimaryAddress":"10.223.10.1","eapMethod":"PEAP","ipv4Address":"10.223.75.46","ipv4AddressSource":"manual","ipv4Gateway":"10.223.75.253","ipv4Subnet":"255.255.255.0","ipv4Vlan":"1","ipv6AddressSource":"NA","ipv6GlobalAddress":"NA","ipv6LinkLocalAddress":"NA","ipv6ULA":"NA","lldpLocationInformation":"NA","lldpNeighbors":"NA","lldpStatus":"active","ntpServer":"Auto","pcPortStatus":"NA","provisioningProtocol":"HTTPS"},"rto":"15","type":"ni"}"}},"enqueuedTime":"2020-05-11T21:59:42.547Z","properties":{"hubName":"ddiaz-iot-iothub-westus2","deviceId":"sampledevice","operationTimestamp":"2020-05-11T21:59:42.3226642Z","iothub-message-schema":"twinChangeNotification","opType":"updateTwin","siteUUID":"$twin.tags.siteUUID","deviceinit":"$twin.tags.deviceinit","networkinfo":"{"data":{"802.1xStatus":"false","cdpStatus":"NA","connectionMode":"half-duplex","connectionSpeed":"1000Mbps","connectionType":"eth0","dnsAlternativeAddress":"","dnsDomain":"polycom.com","dnsPrimaryAddress":"10.223.10.1","eapMethod":"PEAP","ipv4Address":"10.223.75.46","ipv4AddressSource":"manual","ipv4Gateway":"10.223.75.253","ipv4Subnet":"255.255.255.0","ipv4Vlan":"1","ipv6AddressSource":"NA","ipv6GlobalAddress":"NA","ipv6LinkLocalAddress":"NA","ipv6ULA":"NA","lldpLocationInformation":"NA","lldpNeighbors":"NA","lldpStatus":"active","ntpServer":"Auto","pcPortStatus":"NA","provisioningProtocol":"HTTPS"},"rto":"15","type":"ni"}","roomUUID":"fs","primarydeviceinfo":"{"data":{"hardwareModel":"nodejs","hardwareRevision":"7","macAddress":"00:aa:bb:cc:dd:ee","manufacturer":"Polycom","offsetGMT":"-06:00","productFamily":"G7500","serialNumber":"sampledevice","softwareBuild":"212128","softwareRelease":"3.0.1"},"rto":"15","type":"pdi"}","tenantUUID":"t","devicepip":"73.78.223.139","devicemetadata":"{"deviceName":"Mo PolyOS 3.1.1"}"}}]

Still seeing this problem with 10.19 :/

Can also confirm issue still there in 0.10.19

Hi Folks,
Please try our latest version 0.11.1. (There was no update between the issue report to 0.10.19)
We did a major update on the latest release, and would love to know if it is still happening.
Please feel free to reopen if it is still happening.

I am able to see the events now but there is still a glitch with the left side menu expanding to the right.  I need to scroll the application window to see the events.

authors: ShaneOsborne YingXue andrerav damiandiaz76

repo: Azure/azure-iot-explorer


text:
Segmentation fault when importing iothub_client

OS and version used:
Host: ubuntu16 x86_64
embedded os: openwrt

Python runtime used:
python: Python-2.7.12

SDK version used:
sdk: release_2017_08_25

gcc: 4.6.3
Description of the issue:

print Segmentation fault when running ptyhon iothub_client_sample.py
it happened when importing iothub_client
Code sample exhibiting the issue:

import random
import time
import sys
print 'before import iot_client'
import iothub_client
print 'after import iot_client'
Console log of the issue:

before import iot_client
Segmentation fault

can anyone tell me how I should  trace this kind of exception?

I solved it!

How did you solve it?

How did you solve it?

wow, it's been a long time!
It might be caused by libboost_python.
The first time I compiled it , it did not work on my device.
After few days of researching, I found a different way of compiling on the internet. And it worked for me. I cannot remember the website...

repo: Azure/azure-iot-sdk-python


text:
fix: Assign ClientOptions if provided

Currently, the function AttachPolicyClientOptions doesn't do anything because the condition is wrong. Only nil options are assigned, which is not correct.
This PR solves the problem

FYI @AsafMah

Wow, great fix.
I'll release a patch soon.

I'll release a patch soon.

Do you have an ETA? We need this fix in KEDa

Probably tommorow, You can refer directly to the master branch in the meantime though

Fixed in 0.13.0

authors: AsafMah JorTurFer

repo: Azure/azure-kusto-go


text:
Link header returned by StorageDomainManager does not appear to be correct

I'm using the latest version (2.0.0) of the Microsoft.Azure.Mobile.Server.Storage package. The StorageDomainManager returns a uri in the Link header in order for the Azure Client SDK to pull additional items. It appears that the link header is not properly escaped, and this causes an error on the client. Specifically, the datetimeoffset contains a '+' instead of ''%2B'. Here is part of the link header that's being returned:
$filter=(Timestamp%20ge%20datetimeoffset'1970-01-01T00:00:00.0000000+00:00')
The correct value should have been:
$filter=(Timestamp%20ge%20datetimeoffset'1970-01-01T00:00:00.0000000%2B00:00')
Here is the error message that I get if I enter the Url into a browser (this is from the Url that the mobile client is trying to access).
{"message":"The query specified in the URI is not valid: 'Unrecognized 'Edm.DateTimeOffset' literal 'datetimeoffset'1970-01-01T00:00:00.0000000 00:00'' at '14' in '(Timestamp ge datetimeoffset'1970-01-01T00:00:00.0000000 00:00')'.'."}

Can someone please tell me whether these issues are being monitored? If so, what additional information do you need to help resolve this problem?

repo: Azure/azure-mobile-apps-net-server

license_source: bigquery


text:
[Personalizer] Rest API review

Swagger pr
https://github.com/Azure/azure-rest-api-specs/pull/15699
Design link
https://microsoft.sharepoint.com/:w:/t/personalizr/Ebn16DbDmadPuTMggz8FrzIBAsjvBQ4q1X41xsqVMCzkqA?e=qFDOsV

Attending:
@slahabar
@mikekistler
@johanste
@tg-msft
The version should probably be v1.1-preview.2.
JS: Are the authentication protocols all the same here?  Yes.
JS: What is the format of the request bodies?  Just binary, or is there any specification?  There is a definition in the repo.
TG: How is versioning handled for the payload?  It is in the payload.
JS: There should be client libraries for C#, Java, JavaScript, Python.  This is a PLR requirement. You should be planning for that.
Main customer for these APIs is first party, but will be making available to third parties after.
SL: Should we combine these two operations into one?
Keeping separate endpoints seems better from a resource-oriented perspective.
But thinking of these payloads as messages that are just getting posted to EH ... that's not the case tho.
TG: You should have a default response that describes the error response.
Should be the same error response for all operations.
MK: If no response body, then return 204 rather than 200.
Swashbuckle generates the body as "type: string, format: byte" but it should be "type: string, format: binary".
Might need to hand-edit the generated API def to fix this.
TG: Reiterating that the format of the request body should be documented.

authors: mikekistler slahabar

repo: Azure/azure-rest-api-specs