azure-dev-cli_0.9.0-beta.3

0.9.0-beta.3 (2023-05-19)

Features Added

• [2245] Add support to login to Azure Container Registry with current identity.
• [2228] Add error classification and reporting for external errors to azd.
• [2219] Support environment name as explicit argument for azd env refresh.
• [2164] Add timing information on up,package,build, provision,deploy, down and restore commands.

Template Feature

• [2157] Add Dapr and container configuration properties to Azure Container Apps modules.

Bugs Fixed

• [2257] Add purge option of cognitive accounts for azd down.
• [2243] Return error when login fails.
• [2251] Create an alpha version of azure.yaml schema with terraform.
• [2028] Add check on required role assignments for azd pipeline config.

Other Changes

• [2218] Update azd pipeline config default roles to include User Access Administrator.
• [2185] Improve error messages on auth command.

azure-dev-vscode_0.6.0

0.6.0 (2023-05-17)

Features Added

• [#2122] The appropriate schema for azure.yaml has been associated for use by the optional YAML extension. The YAML extension can offer syntax and schema validation, completions, hover tooltips, and more.

Other Changes

• [#2190] Command names have been altered to appear more consistent with VS Code conventions. Commands have been grouped into submenus.

azure-dev-cli_0.9.0-beta.2

0.9.0-beta.2 (2023-05-11)

Bugs Fixed

• [2177] Use information in .installed-by.txt to advise the user on how to upgrade azd
• [2183] Statically link CRT in MSI custom action

azure-dev-cli_0.9.0-beta.1

0.9.0-beta.1 (2023-05-11)

Features Added

• [1808] Support for Azure Spring Apps(alpha feature).
• [2083] Allow resource group scope deployments(alpha feature).

Breaking Changes

• [2066] azd no longer assumes dotnet by default when services.language is not set, or empty in azure.yaml. If you receive an error message 'language property must not be empty', specify language: dotnet explicitly in azure.yaml.
• [2100] As a follow up from the change for azd up ordering, automatic .env file injection when building staticwebapp services have been removed. For more details, read more about Static Web App Dynamic Configuration below.
• [2126] During azd pipeline config commands azd will no longer store non-secret configuration values in GitHub secrets and instead will be stored in GitHub variables. Non-secret variables should be referenced using the vars context instead of the secrets context within your GitHub actions.
• [1989] Refactor Container App service target. Deploy will fail if you are using Azure Container Apps that are not deploying the Azure Container Apps resources as part of the initial provision step.

Bugs Fixed

• [2071] Fix azd config reset causing a logout to occur.
• [2048] Fix azd down deletion on an empty resource group environment.
• [2088] Fix error when running azd pipeline config --provider azdo on Codespaces.
• [2094] Add error check for pipeline yml file and ssh interaction when running azd pipeline config.

Template Fix

• [2013] Fix load template missing error in azd env list.
• [2001] Fix Azure Container Apps CORS strategy for Java, NodeJs and Python.

Other Changes

• [2026] Improve provisioning performance for dotnet services by batching dotnet user-secret updates.
• [2004] Improve error message when no subscriptions are found.
• [1792] Add java postgresql terraform template.
• [2055] Add new starter templates for bicep and terraform.
• [2090] Update todo templates names and descriptions.

Static Web App Dynamic Configuration

This change affects staticwebapp services that are currently relying on azd provided .env file variables during azd deploy. If you have an application initialized from an older azd provided Static Web App template (before April 10, 2023), we recommend uptaking the latest changes if you're relying on .env variables being present. A way to check whether this affects you is by looking at contents in azure.yaml:

Old, uptake needed:

# yaml-language-server: $schema=https://raw.githubusercontent.com/Azure/azure-dev/main/schemas/v1.0/azure.yaml.json

name: <your project>
metadata:
  template: [email protected]
services:
  web:
    project: ./src/web
    dist: build
    language: js
    host: staticwebapp
  api:
    project: ./src/api
    language: js
    host: function

New, no changes necessary:

# yaml-language-server: $schema=https://raw.githubusercontent.com/Azure/azure-dev/main/schemas/v1.0/azure.yaml.json

name: <your project>
metadata:
  template: [email protected]
services:
  web:
    project: ./src/web
    dist: build
    language: js
    host: staticwebapp
    hooks:
      predeploy:
        posix:
          shell: sh
          run: node entrypoint.js -o ./build/env-config.js
          continueOnError: false
          interactive: false
        windows:
          shell: pwsh
          run: node entrypoint.js -o ./build/env-config.js
          continueOnError: false
          interactive: false
  api:
    project: ./src/api
    language: py
    host: function

From the example above, dynamic configuration can still be generated from azd .env files by creating a predeploy hook that embeds the configuration into web assets. See an example change here.

azure-dev-cli_0.8.0-beta.2

0.8.0-beta.2 (2023-04-20)

Features Added

• [#1931] Support *.war and *.ear java archive files, and specify a specific archive file if multiple archives are present.
• [#1704] Add requiredVersions to azure.yaml.
• [#1924] Improve UX on azd down.
• [#1807] Retrieves credentials using the token endpoint on CloudShell.

Bugs Fixed

• [#1923] Fix Python CLI not installed error when Python is installed.
• [#1963] Update GitHub federated auth token provider to allow for fetching of tokens when tokens expire.
• [#1967] Display provisioning resources in Failed state.
• [#1940] Detect and update environment changes before and after hook executions.
• [#1970] Fix pipeline config issues on Codespaces for ghcli and gitcli auth.
• [#1982] Ensure directory has user "execute" permissions.

azure-dev-vscode_0.5.0

0.5.0 (2023-04-05)

Features Added

• [#1849] Support for the azd package command has been added for both the entire application and individual services.

Breaking Changes

• [#1798] Version 0.8.0 or higher of the Azure Developer CLI is now required. If an older version is installed, you will be prompted to update.
• [#1658] Version 1.76.0 or higher of VS Code is now required.

azure-dev-cli_0.8.0-beta.1

0.8.0-beta.1 (2023-04-10)

Features Added

• [#1715] Adding feature alpha toggle:
  • Moving terraform provider as alpha feature. Use azd config set alpha.terraform on to have it enabled.
• [#1833] Deploy from existing package using --from-package flag.

Breaking Changes

• [#1715] Using terraform as provisioning provider will fail and require user to enable terraform running azd config set alpha.terraform on.
• [#1801] Restructuring specific command flags.
  • azd up no longer runs azd init. As a result, the following flags have been removed from azd up:
    • --template / -t
    • --location / -l
    • --branch / -b
    • --subscription
  • Use of --service and --no-progress in azd up is being deprecated.
  • azd deploy now accepts a positional argument. Use azd deploy <web> instead of azd deploy --service <web>
  • Deprecate --no-progress flag as it currently does nothing. A warning message is shown when used.
  • Hide --output flag in the usage printout to correctly reflect the current it's current alpha-preview status. The output contract for structured schema such as JSON has yet been finalized.
• [#1804] Adjust command aliases.
  • azd login and azd logout are now available as azd auth login and azd auth logout respectively. azd login and azd logout are still available for use, but will be removed in a future release.
  • azd infra create and azd infra delete, which have always been aliases for azd provision and azd down, are now deprecated. The commands are still available for use, but will be removed in a future release.
• [#1824] Add working directory sensitivity for restore and deploy.
  • azd deploy will now deploy the current service, when the current working directory is set to a service directory.
  • azd deploy will deploy all services, when the current working directory is set to the project directory containing azure.yaml
  • In other directories, azd deploy will not attempt a deployment and instead error out with suggestions. azd deploy --all can be used to deploy all services, or azd deploy <service> to deploy a given service always.
• [#1752] Ask fewer questions during init.
  • azd init will now only prompt for the environment name. Azure subscription and location values are prompted only when infrastructure provisioning is needed, when running azd provision, and consequently when running azd up.

Bugs Fixed

• [#1734] Fix setting AZURE_PRINCIPAL_ID on multi-tenant directory.
• [#1738] Fix generating auth token on multi-tenant directory.
• [#1762] Allow local files to be kept when running init.
• [#1764] Enhance zip-deploy during build for:
  • Python: Do not include virtual environments for python.
  • Node: Update node modules detection to exclude it from build.
• [#1857] Adds package command hooks to azd schema.
• [#1878] Ensure default generated docker repo/tags are all lowercase.
• [#1875] Fixes panic for postpackage hook errors.

Other Changes

azd up no longer runs azd init

The behavior of azd up -t <template> can be reproduced with:

cd <empty dir>
azd init -t <template>
azd up

azd deploy no longer deploys all services when ran in any directory

The new behavior is as follows:

1. azd deploy will now deploy the current service, when the current working directory is set to a service directory.
2. azd deploy will deploy all services, when the current working directory is set to the project directory containing azure.yaml.
3. In other directories, azd deploy will not attempt a deployment and error out with suggestions. azd deploy --all can be used to deploy all services, or azd deploy <service> to deploy a given service always.

azd up ordering

azd up now packages artifacts prior to running azd provision and azd deploy. This should not affect most users, with the exception of users that may be taking advantage of azd's environment values in packaging staticwebapp services. If azd up no longer works as expected, and you are currently taking advantage of azd's provided environment values to package your application, a predeploy hook may be used to generate configuration files from azd environment values. See the working example in our ToDo templates that leverage staticwebapp, example here. Note that script hooks automatically have azd environment values loaded in the shell environment.

azure-dev-vscode_0.4.2

0.4.2 (2023-03-15)

Bugs Fixed

• [#1735] Fixed an issue with the login command not working immediately after install.

azure-dev-vscode_0.4.1

0.4.1 (2023-03-14)

Bugs Fixed

• [#1724] Refine conditions for displaying the prompt to install the CLI.

azure-dev-vscode_0.4.0

0.4.0 (2023-03-08)

Added

• [#853] Integration with the Azure Resources extension's workspace view. Requires version 0.6.1 of the Azure Resources extension.
• [#1644] Added a walkthrough experience for using the extension.