Add prompts for subscription and location in pipeline config

Add prompts for subscription and location in pipeline config
pipeline config needs the environment is a provision-ready state. Instead of erroring out, we should prompt the user to fill it in. This restores the old behavior prior to #1752.
Fixes #2058

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

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

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

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

MacOS -

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

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

MSI

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

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

Documentation

learn.microsoft.com documentation

title: Azure Developer CLI reference (preview)
description: This article explains the syntax and parameters for the various Azure Developer CLI Preview commands.
author: alexwolftmsft
ms.author: alexwolf
ms.date: 05/01/2023
ms.service: azure-dev-cli
ms.topic: conceptual
ms.custom: devx-track-azdevcli
Azure Developer CLI reference (preview)
This article explains the syntax and parameters for the various Azure Developer CLI Preview commands.
azd
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.
  -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 init: Initialize a new application.
azd monitor: Monitor a deployed application.
azd package: Packages the application's code to be deployed to Azure. (Beta)
azd pipeline: Manage and configure your deployment pipelines.
azd provision: Provision the Azure resources for an application.
azd restore: Restores the application's dependencies.
azd template: Find and view template details.
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
  -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.
      --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                        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
  -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
  -h, --help   Gets help for config.

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

See also

azd config get: Gets a configuration.
azd config list: Lists all configuration values.
azd config 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 unset: Unsets a configuration.
Back to top

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

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

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

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

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
Lists all configuration values.
Synopsis
Lists all configuration values in the configuration path.
The default value of the config directory is:

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

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

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

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
  -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
  -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
  -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 unset
Unsets a configuration.
Synopsis
Removes a configuration in the configuration path.
The default value of the config directory is:

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

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

Examples
azd config unset defaults.location

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

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

See also

azd config: Manage 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
  -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
  -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
  -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.

Back to top

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

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

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

See also

azd env: Manage environments.
Back to top

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

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

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

See also

azd env: Manage environments.
Back to top

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

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

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

See also

azd env: Manage environments.
Back to top

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

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

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

See also

azd env: Manage environments.
Back to top

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

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

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

See also

azd env: Manage environments.
Back to top

azd env set
Manage your environment settings.
azd env set <key> <value> [flags]

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

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

See also

azd env: Manage environments.
Back to top

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

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

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

See also

Back to top

azd monitor
Monitor a deployed application.
azd monitor [flags]

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

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

See also

Back to top

azd package
Packages the application's code to be deployed to Azure. (Beta)
azd package <service> [flags]

Options
      --all                  Deploys all services that are listed in azure.yaml
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for package.

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.
Options
  -h, --help   Gets help for pipeline.

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

See also

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

azd pipeline config
Create and configure your deployment pipeline by using GitHub or Azure Pipelines.
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.
  -e, --environment string      The name of the environment to use.
  -h, --help                    Gets help for config.
      --principal-name string   The name of the service principal to use to grant access to Azure resources as part of the pipeline.
      --principal-role string   The role to assign to the service principal. (default "contributor")
      --provider string         The pipeline provider to use (github for Github Actions and azdo for Azure Pipelines).
      --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.
Back to top

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

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

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

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

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.
azd restore <service> [flags]

Options
      --all                  Restores all services that are listed in azure.yaml
  -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 template
Find and view template details.
Options
  -h, --help   Gets help for template.

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

See also

azd template list: Show list of sample azd templates.
azd template show: Show details for a given template.
Back to top

azd template list
Show list of sample azd templates.
azd template list [flags]

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

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

Options
  -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.
Back to top

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

Options
  -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
  -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

I would like to keep azd pipeline config depending on azd provision (basically locked) until we create a solid strategy for azd pipeline config.

@vhvb1989 I think you brought up some good points in our team meeting yesterday. I feel like this change is additive towards those long-term goals. Let me try to explain.
As you mentioned, it is not quite right that azd pipeline config assumes your current environment is the one you want to set on CI. In the future azd pipeline config will prompt you with something as follows:
 > Would you like to use an existing environment, or create a new one?
The next step is still to ensure that the environment references an AZURE_SUBSCRIPTION_ID, and has AZURE_LOCATION set.
In the current flow, we would recommend the user to first perform azd env new prod, followed by azd pipeline config. I think this works well.
Another thing to think about is whether all environment variables should be transferred to CI. If we start allowing for that, you'd probably want the user to setup the env using azd env set before that. Although this is currently somewhat circular, because the .env file is also the output, and also serves as input -- so there's broadly implications here to think about.

@weikanglim , I talked to someone the other day who was wondering something like this:

I'm trying to refactor our ci/cd pipeline for reliable web applications pattern (not sure if you are familiar with it) and we are using azd for builds and deployments.  I see the azure-dev.yaml that azd recommends, but was wondering if you have patterns documented for moving the project between environments dev->uat->prod  and what is the suggested way of using azd in that scenario.

What's the recommended way of dealign with artifacts etc.

I love what pipeline config does, makes it really simple to do some complicated tasks, that's why I don't want to take it over, but there are couple of blockers that I ran into, such as multiple environments.  It could very easily offer to duplicate the variables in GH as they are setup on the local machine on first run.

Those some some of the ideas which makes me think azd should have a better documentation about common/known CI/CD patterns and how to implement them using azd.
I used to think that, the more flexible azd could be, the better. But even with a lot of flexibility, folks will always want to know what's the story for implementing CI/CD strategies, and how to combine what it is currently offered from existing tools (like GitHub) with azd.
For example, Github has the concept of secrets per environment, and azd could help to create/manage those environments to be mapped to azd environments locally.
Another common strategy on CI/CD is to compile/pack once and deploy multiple times. GitHub provides tools for artifacts and some temas might be looking for a way to do this with azd...  Where they could basically run a pipeline to build and pack, and then use the output to deploy in multiple environments, without rebuild/repackage for each one of them.
These are a few things which leads me to think that before adding more things to pipeline config, we need to first design how azd would help to accomplish any common CI/CD strategy

@vhvb1989 Can you illuminate on how those design decisions impact whether we should ensure an azd environment has AZURE_SUBSCRIPTION and AZURE_LOCATION_ID set?
My take is as follows: regardless of whatever extended feature set we would offer, asking the user to run azd provision before configuring a pipeline to auth with Azure is something I'd consider a product defect, speaking strictly as a user of azd. These two things are not related this way. An analogy here is to say to users that they must provision azure resources before working on a local application.
If you'd like to discuss further about CI/CD strategies, let's create an issue. I've had ideas that have been presented and spoken at lengths. I can see how those could solve the problems we're outlining, but we also want feedback from everyone, including users. Let's seek collective feedback in our issue tracking.

Can you illuminate on how those design decisions impact whether we should ensure an azd environment has AZURE_SUBSCRIPTION and AZURE_LOCATION_ID set?

yes, the impact is for the future. If we decide to change how things work.
I would like to stop looking to ourselves creating changes which requires to consider migrating a current implementation to a new one. For example, if we go ahead with this change and in the future we need to change it, we also need to consider old version to keep working and the process after updating.  That's the main idea why I am trying to abuse of the fact that pipeline config is currently not a critical command or even considered as an starting point... to keep it locked and only visible after the init/up/provision has been explored.  That's adding more time to expend designing where we want to command to be long term and start moving slowly into that direction.

@vhvb1989 The environment variables are synced in CI regardless of this change. This change simply prompts the user instead of requiring the user to run azd provision. Please tell me if I'm missing something...

@vhvb1989 The environment variables are synced in CI regardless of this change. This change simply prompts the user instead of requiring the user to run azd provision. Please tell me if I'm missing something...

Yes, and you can even manually call azd env set to define the sub and location and unlock pipeline config
Or you can copy/paste a previous .env and manually remove/update the values to bridge the azd-prompt and call pipeline config.
What I want is to avoid creating those alternative/undocumented flows without fully embracing the idea about what we want to do and how we want customers to discover the feature and understand what to expect from it.
Right now, for example, we have this documentation: https://learn.microsoft.com/en-us/azure/developer/azure-developer-cli/configure-devops-pipeline which is not telling customers that pipeline config depends on provisioning first, but it is also mentioning that:

Which is currently only true if you are using client-secret authentication.
Then it mentions about federated credential, but only for GitHub.
Lastly, we are telling folks that pipeline command is still beta (https://github.com/Azure/azure-dev/blob/main/cli/azd/docs/feature-stages.md) and creating the idea about breaking changes for beta features are only after customer's feedback. And also telling customers they should only use beta features for non-business-critical scenarios
All that said, I like the idea of making pipeline to move slower and mostly driven by customer feedback.
And also to reduce the places where things can be broken easily as side effects of updating our main flows
Hopefully all of this could be a solid stand on how pipeline command currently looks better as a command standing in the back, away from spotlight and meant not to be a shortcut for fast delegating  provisioning+deploy to a CI/CD agent

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

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

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

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

MacOS -

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

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

MSI

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

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

Documentation

learn.microsoft.com documentation

title: Azure Developer CLI reference (preview)
description: This article explains the syntax and parameters for the various Azure Developer CLI Preview commands.
author: alexwolftmsft
ms.author: alexwolf
ms.date: 05/05/2023
ms.service: azure-dev-cli
ms.topic: conceptual
ms.custom: devx-track-azdevcli
Azure Developer CLI reference (preview)
This article explains the syntax and parameters for the various Azure Developer CLI Preview commands.
azd
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.
  -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 init: Initialize a new application.
azd monitor: Monitor a deployed application.
azd package: Packages the application's code to be deployed to Azure. (Beta)
azd pipeline: Manage and configure your deployment pipelines.
azd provision: Provision the Azure resources for an application.
azd restore: Restores the application's dependencies.
azd template: Find and view template details.
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
  -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.
      --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
  -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
  -h, --help   Gets help for config.

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

See also

azd config get: Gets a configuration.
azd config list: Lists all configuration values.
azd config 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 unset: Unsets a configuration.
Back to top

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

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

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

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

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
Lists all configuration values.
Synopsis
Lists all configuration values in the configuration path.
The default value of the config directory is:

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

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

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

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
  -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
  -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
  -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 unset
Unsets a configuration.
Synopsis
Removes a configuration in the configuration path.
The default value of the config directory is:

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

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

Examples
azd config unset defaults.location

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

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

See also

azd config: Manage 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
  -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
  -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
  -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.

Back to top

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

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

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

See also

azd env: Manage environments.
Back to top

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

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

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

See also

azd env: Manage environments.
Back to top

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

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

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

See also

azd env: Manage environments.
Back to top

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

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

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

See also

azd env: Manage environments.
Back to top

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

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

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

See also

azd env: Manage environments.
Back to top

azd env set
Manage your environment settings.
azd env set <key> <value> [flags]

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

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

See also

azd env: Manage environments.
Back to top

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

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

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

See also

Back to top

azd monitor
Monitor a deployed application.
azd monitor [flags]

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

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

See also

Back to top

azd package
Packages the application's code to be deployed to Azure. (Beta)
azd package <service> [flags]

Options
      --all                  Deploys all services that are listed in azure.yaml
  -e, --environment string   The name of the environment to use.
  -h, --help                 Gets help for package.

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.
Options
  -h, --help   Gets help for pipeline.

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

See also

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

azd pipeline config
Create and configure your deployment pipeline by using GitHub or Azure Pipelines.
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.
  -e, --environment string      The name of the environment to use.
  -h, --help                    Gets help for config.
      --principal-name string   The name of the service principal to use to grant access to Azure resources as part of the pipeline.
      --principal-role string   The role to assign to the service principal. (default "contributor")
      --provider string         The pipeline provider to use (github for Github Actions and azdo for Azure Pipelines).
      --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.
Back to top

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

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

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

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

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.
azd restore <service> [flags]

Options
      --all                  Restores all services that are listed in azure.yaml
  -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 template
Find and view template details.
Options
  -h, --help   Gets help for template.

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

See also

azd template list: Show list of sample azd templates.
azd template show: Show details for a given template.
Back to top

azd template list
Show list of sample azd templates.
azd template list [flags]

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

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

Options
  -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.
Back to top

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

Options
  -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
  -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

@ellismg @vhvb1989 and I chatted offline a little. We aren't too concerned with the approach, but would love your final blessing here to confirm this change is what we want, given the history with #1752

We aren't too concerned with the approach, but would love your final blessing here

Up to you guys. @ellismg @weikanglim.  In a summary, here's what we got:
Good things:

Restoring old behavior.
Remove dependency on other commands (like provision)
azd pipeline config is a powerful command which saves hours of configuration to users.

Nod good things:

Promotes beta feature as entry point (same level of up - provision).
Lack of documentation.  Users don't know things we already know as developers. Like:

Dependency on msgraph access.
Possible collision between the pipeline running and user calling azd up after azd pipeline config
Pipelines are mono-environment. Running azd pipeline config + azd env new foo + azd pipeline config overrides the previous env from pipeline.
A Service Principal is created without any warning or prompt to customer, and there azd down will not remove this SP. There is a potential risk of leaking SP with Contributor access to subscription. User does not know that if they don't use arg --principal-name foo, they are creating a new SP every time and previous SP is just a leak resource on the Azure Active Directory.

So, I still believe this command is not mature enough to be at the same level as the main ones. And that it is something expected beyond the azd basic usage.
For example, someone installing azd and running azd help to see what commands are there...  exploring without any previous investigation from docs about azd (a developer who just heard about this awesome thing called azd and asked choco to install it, for example). I would prefer if the pipeline config will not end up creating a new gh-repo, SP and flow for someone who is only exploring...  I would prefer having a local exploration only... and looking at pipeline as something we want for customers with more experience with azd.
Other notes:

pipeline config was removed from azd as entry point since last release and no customers have created issues to fix this or asking why. Based on that, I am also curios if adding it back is expected/asked from any customer?
Can we wait to hear from customers before deciding what to do?   Why is it better introduce the issue now v/s waiting?
Do we have telemetry about pipeline config which might help us here?

From my analysis, I don't feel strong to approve of give my blessing here.  I don't have the full understanding of what we want for pipeline config from Product, Customer and Engineering perspectives.  But I won't block the PR or stand in the middle if you guys feel it is worth it and better to keep the command as it was in previous releases.

@vhvb1989 Can you log an issue in -pr with those findings? We can distill down what we need to do to improve in those areas.
To be clear, we're simply restoring the old behavior before #1752, so I'm still comfortable with having this in.


🐛 Automated cleaning bug fix in machine template controller

What this PR does / why we need it:
Due to this bug,  automatedCleaning will not be synchronized between
metal3MachineTemplate and metal3Machine when set. Because we are
verifying it from the metal3Machine which should be the metal3MachineTemplate.

/cc @furkatgofurov7 @kashifest
/test-v1b1-integration

/hold

/hold cancel

/test-v1b1-integration

/test-v1b1-integration

/cherry-pick release-0.5


Fix arrowAnnotate example

Bug Fix

Click events was not being removed correctly.
Fix: Make sure to remove all events on dialog before close it.

(Closes issue #554)

Coverage remained the same at 7.244% when pulling afb0c42ffcafb639df82767e8aab478fa63de233 on arrow-annotate-fix-554 into eaeaef55f78a59749fc47911dbc20a4650d58a1d on master.

@galelis you can almost always use your own discretion when choosing to update an example :+1:
This looks good to me. Thanks for taking the time to knock out a fix 🎉


fix 'cant parse page' sql syntax error

had issue on novelupdates where opening novels for the first time will give cant parse page error since sql has wrong syntax

He talking about this


codecvt missing in libstdc++

When compiling with gcc-4.9 and using libstdc++ following error occurs:
In file included from include/jeayeson/detail/parser_util.hpp:20: include/jeayeson/detail/utf.hpp:12:10: fatal error: 'codecvt' file not found #include <codecvt>
How about using boost equivalent?

OK, I've just noticed this:
NOTE: Due to the usage of C++11's <codecvt> for UTF-16 -> UTF-8 transcoding, the current GCC (4.9) is unable to compile JeayeSON. For now, I'm using clang while I consider alternatives.

Sorry for the hassle. I have fixed this issue now (your comment reminded me of it), so you should be able to compile with a modern GCC version (4.9.x works for me).


Add support for Swedish (sv)

Hi!
Just find Your Alfred workflow.
I use the iphone app and it would be grate to search You Version online in Swedish too

Will do! However, I need to set a default version in the language file before I commit. Therefore, please look through the list of Swedish Bible versions at the top of this list and tell me which one is the most popular/widely-used.
Thanks,
Caleb

Okay, I've added Swedish (sv) support on develop branch. @MrMaFurb, please download and test the workflow and let me know if that works for you. :)
Caleb


Fix redis info command

Newer versions of redis do not allow commands with no length
specification, even when there is no arguments.

@eskimoapps @jhansche @jimmithy @piusvelte  Can this be accepted PLEASE?

Considering this has been open for almost 6 years, I'm making a wild assumption this is not going to proceed anytime soon.


Update delegate-it

Follows https://github.com/fregante/delegate-it/releases/tag/v6.0.0

The API may still change due to https://github.com/fregante/delegate-it/pull/46#issuecomment-1522027657

Merging to avoid unnecessary conflicts


Release fixes

Description

Checklist

[ ] Commit sequence broadly makes sense and commits have useful messages
[ ] New tests are added if needed and existing tests are updated
[ ] When applicable, versions are updated in .cabal and CHANGELOG.md files according to the
versioning process.
[ ] The version bounds in .cabal files for all affected packages are updated. If you change the bounds in a cabal file, that package itself must have a version increase. (See RELEASING.md)
[ ] All visible changes are prepended to the latest section of a CHANGELOG.md for the affected packages. New section is never added with the code changes. (See RELEASING.md)
[x] Code is formatted with fourmolu (use scripts/fourmolize.sh)
[x] Cabal files are formatted (use scripts/cabal-format.sh)
[x] hie.yaml has been updated (use scripts/gen-hie.sh)
[ ] Self-reviewed the diff

Superseded by https://github.com/IntersectMBO/cardano-ledger/pull/4409


npm run build creates 2 .js files.

Thanks for creating this boilerplate.
I have an issue when bundling files for production build.
npm run build command creates 2 .js files. I want to bundle everything into single .js file.
Can you please help to achieve this ?
Thanks in advance.

Hey @indikaUih.  If you want to remove the code splitting you can go for it by removing
   optimization: {             splitChunks: {                 chunks: "all",             },         },
inside webpack.config.ts.

Hey @indikaUih. If you want to remove the code splitting you can go for it by removing
 optimization: { splitChunks: { chunks: "all", }, },
inside webpack.config.ts.

Worked !!!! Thanks very much.


Agenda: 8th May 2018

Please note we've moved back to the main community channel (#rust-community) to increase our reach. Once we've reached sufficient momentum we'll move back to the #rust-content.
5:30-6pm UTC on #rust-community on irc.mozilla.org. EIAL (Easy IRC Access Link): https://kiwiirc.com/client/irc.mozilla.org:+6667/#rust-community
Agenda

Announcements - @booyaa 5mins
Content-o-Tron Global Sprint 10-11th May - @booyaa 10mins

15 mins remaining
Please comment below if you wish to add anything to the agenda!

potential call for blog posts: how you got into rust (use the #rustreach hashtag, the program kicks off may 15th so it might be cool to have community members write stories about how they got into rust as a way of motivation for the new participants as they start their journey)


When signing up, email says "User XXX at example.com ..."

When signing up for a new account, I received a confirmation email but the contents of the email received were:

User abe at example.com has given this as an email address.
To confirm this is correct, go to ...

(Where '...' was the link back to gennotes).  I used the web site http://gennotes.herokuapp.com.
Also, the 'from' account was 'webmaster@localhost' (via mailgun.org).
Registration and signup worked otherwise.

Fixed the Sites object to use "gennotes.herokuapp.com" and "GenNotes" instead of the default "example.com" data.


[BUG] Trigger selectedIndex change for BottomNavigation do not apply active color on IOS

Which platform(s) does your issue occur on?

[x] iOS
[ ] Android

What type of device?

[x] Emulator
[ ] Device

Please, provide the following version numbers that your issue occurs with:

CLI: 6.1.2
Cross-platform modules: 6.1.1
Runtime(s): 6.1.1
Plugin(s):

Please, tell us how to recreate the issue in as much detail as possible.
Describe the steps to reproduce the behavior:
bind selectedIndex to a variable :
<BottomNavigation ref='NavigationBottom' @selectedIndexChanged='selectedIndex = $event.newIndex'     :selectedIndex='selectedIndex'>[TabStrip...]</BottomNavigation>
trigger a change in typescript :
this.selectedIndex = 3; ( select the last tab )
on android it it working fine, on IOS content change ( so change is correctly triggered ) but the active color is not apply to the current selected tab and is not remove from the old index
see video for visual on Android and IOS : https://youtu.be/tammsYHAZeA
( blue button with 'ff' is the trigger )

@henrychavez  This bug has been fixed, but I still see this bug, thank you


Complete URS request for review of website for DNS switch

💡 Description

URS315130 submitted. Awaiting approvla

Quick FYI @jordanpadams we do have URS304382 and clearance CL#22-5090 for planetarydata.org.
Maybe we request re-review of that? I don't know what the procedure is 🤷♀

@nutjob4life I referenced those in the new one, and I selected to check new content, vs a new site altogether.

@jordanpadams copy that! 📡

Done! URS315130 approved


Roll back 2.0.0 changes

Problem: we're wanting to make clear documentation etc for pluto-encrypted. Currently we have all these 2.0.0 modules published which are a distraction for new users because:

they are the first thing you see when you go to this repo
they don't work with the current SDK
from what I understand you aren't that keen on the "upgrade RXDB" path anyway

Proposal

wind the HEAD back to before these releases
move the 2.0.0 work into a branch called "rxdb_upgrade"
remove the 2.0.0 tags
unpublish 2.0.0 packages from npm

The goal of all this is to make it real hard for people to accidentally install broken software setup / be reading the wrong docs

@elribonazo what do you think?


Suggested Changes for Quantity Picker Implementation

This PR is a replacement of the following PR. The main advantage of this PR is that we aren't using 2 different implementations of the quantity picker. This means that if there are changes to the UI or default functionality it's only done in one place.

UX/UI Review

[ ] Buttons for the quantity pickers aren't keyboard accessible for desktop. See recording.
[ ] Can we center the number the input?  See screenshot
[ ]


Add E2E tests for Docker and Containerd

AC:

Both Docker and Containerd clusters are properly tested

this has been done in new generated tests


Add delete and archive feature

Some of the unit and instrumented tests are failing because of removed VerifiableCredentialDao class. Could you please fix those as part of this PR?


libtxt: Implement OpenType locl support

Some fonts have different variant glyphs based on the locale. This is critical for Chinese, Chinese (Simplified), Japanese, and Korean; it is also used for other scripts (e.g. Latin vs Romanian).
OpenType encodes this using the locl feature tag.
There are some resources to test this online, e.g. the LOCL Test font.
It is common to not know what locale to use. In that case, we should default to no locale and allow the font to pick its default.

[ ] Pass the locale through from the framework to the engine. Each TextSpan should take an optional Locale; by default it should inherit the value from ParagraphStyle which should have a Locale also.
[ ] Use the locale in the engine to configure the font rendering by setting it in the minikin::TextStyle structure.
[ ] Test this.

How do I pass the locale to the ui.TextStyle?

If you're down at that level of the system, you can just pass it to the ui.TextStyle constructor.
If you're at a higher level, we haven't yet added it to the framework. I've filed https://github.com/flutter/flutter/issues/16408 to cover this.


multiple result sets

SQL Operations Studio Version: sqlops 0.26.7 (723c7cb3bfd80d87fc8a1141632089cd4808495c, 2018-02-16T21:34:47.034Z)
OS Version: Windows_NT x64 6.1.7601
Extensions: none

Steps to Reproduce:

create sql containing multiple separate select statements, in my case it was 7, make sure only 4th and 5th return results, other should not return anything.
Scroll down through results and when you get to 4th there will be a few seconds delay before 4th grid with results shows up, it creates a false impression that none of the queries have results.
After 4th grid with results shows, scroll up back to first result and go back to 4th again, the same issue, it will take a few seconds before 4th grid shows up.

forgot to mention if you scroll up/down fast enough 4th and 5th result will never show up.

I can't reproduce this exact issue, but I'm also having issues with multiple result sets so I'll tack onto this issue:
If I have 7 or fewer result sets I'm seeing results in grid view and the Messages pane shows correct information for rows affected, but once I go over 7 result sets the grid view shows place holders for the result columns and the Messages pane shows correct information for rows affected, but there is only data in the grid view for the first 4 sets of data.

@IsItGreyOrGray regarding your issue, we have optimizations that if there are more than a certain amount of result sets (i think it was 8) we only render what is currently on screen, otherwise there are bad performance issues. Sounds like this optimization might not be working properly.
Is it when you scroll the results don't render?

Sorry about the late response...
If I scroll, should the newly "visible" result sets currently on the screen be rendered? If so, they're not. It looks like once I hit 8 result sets it will only ever show me what was visible on the screen to begin with.
I've been playing around and this is what I see...
Using 7 select statements:
I get all result sets

Using 8 select statements:
If I drag the Results pane as small as I can , it will render the result sets visible on screen (2) and the rest will be empty.

If I drag the Results pane as tall as I can , it will render the result sets visible on screen (5) and the rest will be empty.

We have lots of stored procedures that return multiple result sets and this bug is making Ops Studio almost unusable for us
The following code will trigger the issue in Version 0.28.6, run it, and the results sets (for me) for 3 - 10 are blank (I can see some results for 3 - 10 being painted as the queries execute, but once the whole batch is complete then the result sets are empty)
select top 100 2, * from  sys.objects; WAITFOR DELAY '00:00:01';
select top 100 3, * from  sys.objects; WAITFOR DELAY '00:00:01';
select top 100 4, * from  sys.objects; WAITFOR DELAY '00:00:01';
select top 100 5, * from  sys.objects; WAITFOR DELAY '00:00:01';
select top 100 6, * from  sys.objects; WAITFOR DELAY '00:00:01';
select top 100 7, * from  sys.objects; WAITFOR DELAY '00:00:01';
select top 100 8, * from  sys.objects; WAITFOR DELAY '00:00:01';
select top 100 9, * from  sys.objects; WAITFOR DELAY '00:00:01';
select top 100 10, * from  sys.objects; WAITFOR DELAY '00:00:01';

@anthonydresser this looks very much like the repro for #1118 - are these all duplicate issues? If so what can we do to resolve?

I'm going to close this as a duplicate of https://github.com/Microsoft/sqlopsstudio/issues/156 so we can track this work in one place.  Please leave related feedback in https://github.com/Microsoft/sqlopsstudio/issues/156.


Permissions error using downloadbuildartifact.  What Permisions???

Note
Issues in this repo are for tracking bugs, feature requests and questions for the tasks in this repo
For a list:
https://github.com/Microsoft/azure-pipelines-tasks/tree/master/Tasks
If you have an issue or request for the Azure Pipelines service, use developer community instead:
https://developercommunity.visualstudio.com/spaces/21/index.html )
Required Information
Entering this information will route you directly to the right team and expedite traction.
Question, Bug, or Feature?
Type: Question
Enter Task Name: DownloadBuildArtifacts@0
list here (V# not needed):
https://github.com/Microsoft/azure-pipelines-tasks/tree/master/Tasks
Environment

Server - Azure Pipelines or TFS on-premises? Azure Pipelines

If using TFS on-premises, provide the version:

If using Azure Pipelines, provide the account name, team project name, build definition name/build number: iMSTraining/RMS, RMS, 14.08.1002.0

Agent - Hosted or Private: Private

If using Hosted agent, provide agent queue name:

If using private agent, provide the OS of the machine running the agent and the agent version: Windows 10 (Version 10.0.18363.959), vsts-agent-win-x64-2.168.2

Issue Description
We are getting a permission related error but don't know what permissions are missing.  The build artifact does exist.
Task definition:
 # Download build artifacts
    # Download files that were saved as artifacts of a completed build
    - task: DownloadBuildArtifacts@0
      displayName: 'Download latest TestTool build'
      inputs:
        buildType: 'specific' # Options: current, specific
        project: 'TestTool' # Required when buildType == Specific
        pipeline: 'TestTool-bld' # Required when buildType == Specific
        #specificBuildWithTriggering: false # Optional
        buildVersionToDownload: 'latest' # Required when buildType == Specific. Options: latest, latestFromBranch, specific
        allowPartiallySucceededBuilds: false # Optional
        branchName: 'refs/heads/master' # Required when buildType == Specific && BuildVersionToDownload == LatestFromBranch
        #buildId: # Required when buildType == Specific && BuildVersionToDownload == Specific
        #tags: # Optional
        downloadType: 'single' # Choose whether to download a single artifact or all artifacts of a specific build. Options: single, specific
        artifactName: 'TestTool' # Required when downloadType == Single
        itemPattern: '**/**' # Optional
        downloadPath: '$(Build.ArtifactStagingDirectory)'
        parallelizationLimit: '8' # Optional

Failed in getBuildDefinitions with error: Error: VS800075: The project with id 'vstfs:///Classification/TeamProject/d45ac940-5773-4d4f-a1d9-79206b0b4ba0' does not exist, or you do not have permission to access it.

Task logs
##[debug]check path : C:\EvolveiMS\Agent_work_tasks\DownloadBuildArtifacts_a433f589-fce1-4460-9ee6-44a624aeb1fb\0.167.2\node_modules\artifact-engine\lib.json
##[debug]adding resource file: C:\EvolveiMS\Agent_work_tasks\DownloadBuildArtifacts_a433f589-fce1-4460-9ee6-44a624aeb1fb\0.167.2\node_modules\artifact-engine\lib.json
##[debug]system.culture=en-US
##[debug]check path : C:\EvolveiMS\Agent_work_tasks\DownloadBuildArtifacts_a433f589-fce1-4460-9ee6-44a624aeb1fb\0.167.2\task.json
##[debug]adding resource file: C:\EvolveiMS\Agent_work_tasks\DownloadBuildArtifacts_a433f589-fce1-4460-9ee6-44a624aeb1fb\0.167.2\task.json
##[debug]system.culture=en-US
##[debug]buildType=specific
##[debug]specificBuildWithTriggering=false
##[debug]buildVersionToDownload=latest
##[debug]allowPartiallySucceededBuilds=false
##[debug]branchName=refs/heads/master
##[debug]downloadPath=C:\EvolveiMS\Agent_work\10\a
##[debug]downloadType=single
##[debug]tags=null
##[debug]System.TeamFoundationCollectionUri=https://dev.azure.com/iMSTraining/
##[debug]SYSTEMVSSCONNECTION auth param AccessToken = ***
##[debug]VSTS_HTTP_RETRY=undefined
##[debug]release.triggeringartifact.alias=undefined
##[debug]definition=TestTool-bld
##[debug]project=TestTool
##[debug]buildId=null
Error: in getBuildDefinitions, so retrying => retries pending  : 4
Error: in getBuildDefinitions, so retrying => retries pending  : 3
Error: in getBuildDefinitions, so retrying => retries pending  : 2
Error: in getBuildDefinitions, so retrying => retries pending  : 1
##[error]Failed in getBuildDefinitions with error: Error: VS800075: The project with id 'vstfs:///Classification/TeamProject/d45ac940-5773-4d4f-a1d9-79206b0b4ba0' does not exist, or you do not have permission to access it.
##[debug]Processed: ##vso[task.issue type=error;]Failed in getBuildDefinitions with error: Error: VS800075: The project with id 'vstfs:///Classification/TeamProject/d45ac940-5773-4d4f-a1d9-79206b0b4ba0' does not exist, or you do not have permission to access it.
##[debug]SYSTEM.HOSTTYPE=build
##[debug]BUILD.DEFINITIONNAME=RMS
##[debug]BUILD.BUILDID=118
##[debug]SYSTEM.TEAMFOUNDATIONSERVERURI=https://dev.azure.com/iMSTraining/
##[debug]SYSTEM.TEAMPROJECT=RMS
##[debug]BUILD.BUILDID=118
##[debug]TASK.DISPLAYNAME=Download latest TestTool build
##[debug]SYSTEM.JOBID=3dc8fd7e-4368-5a92-293e-d53cefc8c4b3
##[debug]AGENT.VERSION=2.168.2
##[debug]AGENT.OS=Windows_NT
##[debug]AGENT.NAME=5CG70948WR
##[debug]Processed: ##vso[telemetry.publish area=DownloadBuildArtifacts;feature=reliability]{"hostType":"build","definitionName":"[NonEmail:RMS]","processId":"118","processUrl":"https://dev.azure.com/iMSTraining/RMS/_build?buildId=118","taskDisplayName":"Download latest TestTool build","jobid":"3dc8fd7e-4368-5a92-293e-d53cefc8c4b3","agentVersion":"2.168.2","agentOS":"Windows_NT","agentName":"5CG70948WR","version":{"Major":0,"Minor":167,"Patch":2},"issueType":"error","errorMessage":"{"stack":"Error: VS800075: The project with id 'vstfs:///Classification/TeamProject/d45ac940-5773-4d4f-a1d9-79206b0b4ba0' does not exist, or you do not have permission to access it.\n    at RestClient. (C:\\EvolveiMS\\Agent\\_work\\_tasks\\DownloadBuildArtifacts_a433f589-fce1-4460-9ee6-44a624aeb1fb\\0.167.2\\node_modules\\typed-rest-client\\RestClient.js:200:31)\n    at next (native)\n    at fulfilled (C:\\EvolveiMS\\Agent\\_work\\_tasks\\DownloadBuildArtifacts_a433f589-fce1-4460-9ee6-44a624aeb1fb\\0.167.2\\node_modules\\typed-rest-client\\RestClient.js:6:58)\n    at process._tickCallback (internal/process/next_tick.js:109:7)","message":"VS800075: The project with id 'vstfs:///Classification/TeamProject/d45ac940-5773-4d4f-a1d9-79206b0b4ba0' does not exist, or you do not have permission to access it.","statusCode":400,"result":{"message":"VS800075: The project with id 'vstfs:///Classification/TeamProject/d45ac940-5773-4d4f-a1d9-79206b0b4ba0' does not exist, or you do not have permission to access it."}}"}
##[debug]task result: Failed
##[error]Error: VS800075: The project with id 'vstfs:///Classification/TeamProject/d45ac940-5773-4d4f-a1d9-79206b0b4ba0' does not exist, or you do not have permission to access it.
##[debug]Processed: ##vso[task.issue type=error;]Error: VS800075: The project with id 'vstfs:///Classification/TeamProject/d45ac940-5773-4d4f-a1d9-79206b0b4ba0' does not exist, or you do not have permission to access it.
##[debug]Processed: ##vso[task.complete result=Failed;]Error: VS800075: The project with id 'vstfs:///Classification/TeamProject/d45ac940-5773-4d4f-a1d9-79206b0b4ba0' does not exist, or you do not have permission to access it.
Finishing: Download latest TestTool build
Troubleshooting
Checkout how to troubleshoot failures and collect debug logs: https://docs.microsoft.com/en-us/vsts/build-release/actions/troubleshooting
Error logs
[Insert error from the logs here for a quick overview]

Any update on this?  Still having the same problem.  I have confirmed via the API that the project id in the error message exists.

The project with id 'vstfs:///Classification/TeamProject/d45ac940-5773-4d4f-a1d9-79206b0b4ba0'

I too have the same issue as mentioned above.
Same error - Error: VS800075: The project with id 'vstfs:///Classification/TeamProject/xxxxxxxxxxxxxxxxxxxxxxxxx' does not exist, or you do not have permission to access it.
Anything on this yet?

Still waiting on ANY response!

Hi,
I solved the same error using this post
[https://developercommunity.visualstudio.com/content/problem/1146258/error-vs800075-when-downloading-artifact-from-anot.html]

@RajashriVadakeri I will take a look.  Thank you.

@RajashriVadakeri thank you so much.  That has it solved!


fix: allow installing via git

Without this change npm i github:not-an-aardvark/snoowrap fails as the compile script isn't ran.

LGTM. Thanks!


Fix show_excerpts in collection layout's front matter

This is a bug fix.
Summary
The show_excerpts front matter in collection layout doesn't work as documented for now. Fixed it.

not stale


weight in responses

Just starting to work through the tutorial, it seems that the weight in responses doesn't work as expected. While executing many times
+ greetings
- Hi there!{weight=20}
- Hello!{weight=25}
- Yos kyoco duckeb!

responses come in not weighted. Cause is probably the implementation of weights (brain.py line 376)
               #Process weights in the replies.
               bucket = []
               for text in matched["reply"]:
                   weight = 1
                   match  = re.search(RE.weight, text) # original re.match
                   if match:
                       weight = int(match.grou

that is my modified version originally it used re.match instead of re.search, but match only matches at the beginnig of a string (if I recall correctly)

@gerhard-gs68 You're correct at identifying this bug. You can make a merge request to fix this?

@Dinh-Hung-Tu never done before on github but I will studyand give it a try with next week.

@gerhard-gs68 Can I help you do this fix if you don't have time?

Fixed by PR #106


Csproj intellisense

Have the latest VS 2017 RC. Trying out the new csproj based .NET Core project.
Question: Is there supposed to be intellisense of any kind when editing csproj? Even for basic stuff like OutputType and TargetFramework.
Cause I have only Autocompletion for existing elements, but no Intellisense.
Not sure if there is a problem, or it's just not implemented.
Another question: Is there a documentation draft/wiki on the new csproj format? What kind of settings are available, the format, etc. Can find anything for the "modern" csproj.

@byyyt, how are you editing the project file? I tested this with the latest internal build and have intellisense working correctly. @RaulPerez1

Well, Open the project file with "Edit .csproj" from context menu. Nothing fancy, just default Console project file. Well I do have the "latest" publicly available VS 2017 Enterprise RC.

Cause I have only Autocompletion for existing elements, but no Intellisense.

I think that what you're seeing is what's currently implemented, e.g. you're getting the list with available tags but you don't get a list of available values once the tag is inserted. Can you confirm that my statement is accurate into what you're seeing and expecting?

This requires a msbuild language service which is tracked by https://github.com/dotnet/roslyn-project-system/issues/766


Writing files to eu2 IDL

Describe the bug
When I try to write files with the MindConnect Node-RED agent to the IDL on an EU2 tenant, he file upload fails. A signed URL is created, and this one works, but the upload later fails
To Reproduce
Steps to reproduce the behavior:

Create a flow that sends a payload via Agent
Watch the output, it contains a working signed url
check in IDL Data Explorer
File has not arrived
5.  (Bonus) Upload the payload with the created signed url manually - file arrives in IDL

Expected behavior
The agent should upload the file
** MindSphere Plan **

iot value plan eu2

Additional context
I would assume that the error lies in the header when uploading the payload. For eu2 the following has to be set
"x-ms-blob-type" : "BlockBlob"

@peterandree thank you, I don't have access to data lake on EU2, so I can't test this yet, at the time the functionality was created there was no EU2 instance available. Can you live with manual upload for now, as this needs to be fixed in the underlying library and not in the node?


TI SensorTag Sensors does not work properly on Nexus 7

Problem: There are issues with TI SensorTag Sensors on Nexus 7, because the Nexus 7 only reports devices found during scan once. The logic in the example app is written in a faulty way that assumes each device reported continuously.
Solution: Rewrite application logic.

This issue should be solved in the refactored TI SensorTag library in release 1.2.0.


override hourText and minuteText

hi, It's me again.~
Now I'm using this datatimefield and it was useful,but I still can't override the hourText and minuteText.

So I think there was a little change in the code will solve the problem.

I change the file DateTimePicker.js
fieldLabel: me.hourText
to
fieldLabel: me.pickerField.hourText ? me.pickerField.hourText : me.hourText
and
fieldLabel: me.minuteText
to
fieldLabel: me.pickerField.minuteText ? me.pickerField.minuteText : me.minuteText

It works...

This should fix your issue
Ext.define('Ext.ux.DateTimeField',{
    override: 'Ext.ux.DateTimeField',
    createPicker: function() {
        var me = this,
            parentPicker = this.callSuper(),
            o = {}, key;
        for(key in parentPicker) {
            if (parentPicker.hasOwnProperty(key) && parentPicker[key]){
                o[key] = parentPicker[key];
            }
        }

        for (key in me.initialConfig) {
            if (me.initialConfig.hasOwnProperty(key) && me.initialConfig[key]) {
                o.initialConfig[key] = me.initialConfig[key];
            }
        }

        return Ext.create('Ext.ux.DateTimePicker', o);
    }
});


Values changed between the scans

How could I know which value has changed between two scans using scanflow? Does scanflow support this function now? Or maybe I should develop a ValueScaner and implement this function myself? Please let me know, Thanks!

You can use p command to print the current values.


add gitattributes to reduce composer package size

adding all files to .gitattributes, which the composer package don't need.
Should always include:

Pipline/Github Actions
Tests Files
Docs
etc.

Thanks! I always wondered what that file was for, now I know.

you can do much more with it, but for the beginning it is enough :)


process monitors

@ericsciple Do we still want to merge this?

@ericsciple can I close here or do we still want this?


todo: Add --pretty output

The 'todo list' output currently only shows the Todo ID, and a link to the
Todo item.  The WebUI outputs additional information such as the state of
the Merge Requests and Issues, how the Todo entry was added to the Todo
list, etc.
Add an option, --pretty, to output the additional information.
Signed-off-by: Prarit Bhargava<EMAIL_ADDRESS>

@bmeneg, the pretty output is a tad slower than the normal output.  This is because the pretty output does an status lookup on each MR and Issue in the Todo list.

@bmeneguele after fighting with different formats for this, I decided on keeping the --pretty format as is.  While it doesn't 100% confirm to the Todo list in the WebUI I would argue that because we have to include the TodoID, the web URL, and an explanation and I want it in a machine readable format, there's only so many ways to parse the data.


Cannot place Biomes O' Plenty flowers on mulch blocks

Not sure if this is a compatibility issue as the mulch accepts flowers from other mods and the BoP flowers can be placed onto such things as modded flower pots.

Biomes O Plenty bug, they need to return EnumPlantType.Plains from getPlantType for their block.

Thanks for the replay. I opened an issue with Biomes O' Plenty.

Looks like Biomes O' Plenty closed the issue on their tracker. As there is nothing I can do without hacks on my side, I will just have to call their plants unsupported.


Error setting up entry... alexa_media (Echo) - HA 2022.3.3

After the update to version 2022.3.3 once again a new problem. But I am used to that by now.
This error originated from a custom integration.

Logger: homeassistant.config_entries
Source: custom_components/alexa_media/__init__.py:324
Integration: Alexa Media Player (documentation, issues)
First occurred: 11:45:54 AM (1 occurrences)
Last logged: 11:45:54 AM

Error setting up entry<EMAIL_ADDRESS>- amazon.com for alexa_media
Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/alexapy/aiohttp/connector.py", line 1154, in _create_direct_connection
    hosts = await asyncio.shield(host_resolved)
  File "/usr/local/lib/python3.9/site-packages/alexapy/aiohttp/connector.py", line 880, in _resolve_host
    addrs = await self._resolver.resolve(host, port, family=self._family)
  File "/usr/local/lib/python3.9/site-packages/alexapy/aiohttp/resolver.py", line 33, in resolve
    infos = await self._loop.getaddrinfo(
  File "/usr/local/lib/python3.9/asyncio/base_events.py", line 856, in getaddrinfo
    return await self.run_in_executor(
  File "/usr/local/lib/python3.9/concurrent/futures/thread.py", line 58, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/usr/local/lib/python3.9/socket.py", line 954, in getaddrinfo
    for res in _socket.getaddrinfo(host, port, family, type, proto, flags):
socket.gaierror: [Errno -3] Try again

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/local/lib/python3.9/site-packages/alexapy/helpers.py", line 137, in wrapper
    return await func(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/alexapy/alexalogin.py", line 574, in login
    if await self.test_loggedin(cookies):
  File "/usr/local/lib/python3.9/site-packages/alexapy/alexalogin.py", line 455, in test_loggedin
    get_resp = await self._session.get(
  File "/usr/local/lib/python3.9/site-packages/alexapy/aiohttp/client.py", line 535, in _request
    conn = await self._connector.connect(
  File "/usr/local/lib/python3.9/site-packages/alexapy/aiohttp/connector.py", line 542, in connect
    proto = await self._create_connection(req, traces, timeout)
  File "/usr/local/lib/python3.9/site-packages/alexapy/aiohttp/connector.py", line 907, in _create_connection
    _, proto = await self._create_direct_connection(req, traces, timeout)
  File "/usr/local/lib/python3.9/site-packages/alexapy/aiohttp/connector.py", line 1166, in _create_direct_connection
    raise ClientConnectorError(req.connection_key, exc) from exc
alexapy.aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host www.amazon.com:443 ssl:<ssl.SSLContext object at 0x7f7b344d40> [Try again]

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/config_entries.py", line 335, in async_setup
    result = await component.async_setup_entry(hass, self)
  File "/config/custom_components/alexa_media/__init__.py", line 324, in async_setup_entry
    await login.login(cookies=await login.load_cookie())
  File "/usr/local/lib/python3.9/site-packages/alexapy/helpers.py", line 147, in wrapper
    raise AlexapyConnectionError from ex
alexapy.errors.AlexapyConnectionError

Restarts of course have not changed anything.
It is so annoying!

I have the same problem with all Alexa Media Player Entitles.  It all started after I updated to 2022.3.3.  After the failure I did a complete restore of my System to 2022.2.9 but still having the same problem.  I reinstall Alexa Media Player in HACS and do the Integration install.  Everything seemed to work until the final step when I receive the following error "Error 500 Internal Server Error Server got itself in trouble"  I tried to talk to Amazon support but that was a real waste of time,  Any help would be greatly appreciated.  Also my Alexa Guard is no longer working either.

Your HA can't connect to alexa.amazon.com for some reason. It may be your SSL certs or it may be some other network issue. Unfortunately based on the logs, the component can't resolve that for you.


common application shortcuts

It would be useful to handle some common application shortcuts by default.
Ctrl + O for new document opening for example.

Ctrl + O for new document opening for example.

Use Alt F L (or Alt F ) to load a file. When you press the Alt key common shortcuts that can be used with the Alt key gets underlined in the menubar and the sidebar. You can also drop a file on the Program list or 3D View to load it.


Startup fails after migration

I've just moved my ldap setup from one server to another by simply copying over all files (config, database in host directories, environment.yml and ssl certificates) and tried starting the container.
This fails with the following error:
Check previous TLS certificates...
Hi! I'm ssl-helper, what button should i press ?
cfssl-helper is launched, everybody on the floor!
Files /container/run/service/slapd/assets/certs/fullchain.pem and /container/run/service/slapd/assets/certs/key.pem exists, fix files permissions
Start OpenLDAP...
Waiting for OpenLDAP to start...
595be0a3 @(#) $OpenLDAP: slapd  (Jan 16 2016 23:00:08) $
	root@chimera:/tmp/buildd/openldap-2.4.40+dfsg/debian/build/servers/slapd
595be0a3 daemon: bind(7) failed errno=99 (Cannot assign requested address)
595be0a3 slapd stopped.

Any ideas what could be going wrong here?
(A simple docker run oisixia/openldap works by the way)

After some more try and error, I believe this is a  problem of docker-compose. The following composition worked well in coreOS but doesn't in debian stretch.
version: '2'

services:
    # dummy nginx for tls certificate generation
    ldap_nginx_dummy:
        container_name: ldap_nginx_dummy
        image: nginx
        restart: always
        environment:
            VIRTUAL_HOST: "ldap2.domain.tld"
            LETSENCRYPT_HOST: "ldap2.domain.tld"
            LETSENCRYPT_EMAIL<EMAIL_ADDRESS>        volumes:
            - /data/ldap/nginx_conf.d:/etc/nginx/conf.d:ro
        networks:
            - outside
    # ldap container
    ldap:
        container_name: ldap
        image: osixia/openldap
        build:
            context: ./src/docker-openldap/image
        restart: always
        hostname: ldap2.domain.tld
        domainname: domain.tld
        volumes:
            - ./database:/var/lib/ldap
            - ./config:/etc/ldap/slapd.d
            - /data/ssl/ldap2.domain.tld:/container/service/slapd/assets/certs
            - ./environment:/container/environment/01-custom
        networks:
            - inside
            - outside
        ports:
            - "389:389"
            - "636:636"
        command: "--loglevel trace --copy-service"

networks:
    inside:
    outside:
        external:
            name: proxy-tier

In deboian this keeps bootlooping.
Running the docker command directly lwokrs perfectly well for me.
docker run --name ldap --hostname ldap2.domain.tld -p 389:389 -p 636:636 --net proxy-tier --volume /data/ldap/database:/var/lib/ldap --volume /data/ldap/config:/etc/ldap/slapd.d --volume /data/ssl/ldap2.domain.tld:/container/service/slapd/assets/certs --volume /data/ldap/environment:/container/environment/01-custom --rm dasmaeh/openldap --copy-service

I actually can't see the difference between the two.

Unfortunately I met the same problem when i copied the config and database dir from a running docker-openldap node for replication. The replication operation is fine and runs well in test env but cannot start container in prod, it's so weird...

I had a similar issue solved by removing the domainname parameter from the docker-compose.yml file