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.