This post announces that the September 2024 release (version 1.10.0) of the Azure Developer CLI (azd) is now available. As always, you can learn about how to get started with the Azure Developer CLI by visiting our documentation.

Here’s what’s new with azd:

• Remote builds support with Azure Container Registry (azure-dev#509)
• Multiple hooks per event (azure-dev#4257)
• Add GitHub as template source configuration option (azure-dev#4203)
• Support for Java Azure Functions (azure-dev#4155)
• Alpha feature: Deployment stacks (azure-dev#4144)
• Resource group scoped deployments promoted to beta (azure-dev#2995)

Remote builds support with Azure Container Registry

We’re making it easier for you to work with Docker and Azure Container Apps (ACA) with the help of Azure Container Registry (ACR). We now support using the ACR remote build feature when your app host is containerapp. This means you can now avoid the complexity of using local tooling to build Docker containers. To use this new feature, add the following to the docker member of a service in your azure.yaml file:

    remoteBuild: true

A full example of an azure.yaml file using this feature may look like:

name: yourApp-aca
metadata:
    template: yourApp-aca@0.0.1-beta
services:
  api:
    project: ./src/api
    language: js
    host: containerapp
    docker:
      remoteBuild: true

Multiple hooks per event

azd now offers support for multiple hooks per event. For example, post-provision, you could now run a custom azd operation hook and then a more generic script hook. In practice, support for multiple hooks per event looks like:

name: example-project
services:
    api:
        project: src/api
        host: containerapp
        language: ts
        hooks:
            postprovision:
                - shell: sh
                  run: scripts/postprovision1.sh
                - shell: sh
                  run: scripts/postprovision2.sh
hooks:
    postprovision:
        - shell: sh
          run: scripts/postprovision1.sh
        - shell: sh
          run: scripts/postprovision2.sh

We’re eager to learn what you do with the expanded support! So, feel free to show off what you build in the show and tell category in our GitHub discussion board.

Add GitHub as template source configuration option

Last September, we released the ability to configure template sources. And this September, we’re happy to add a new template source option: GitHub (gh). Adding a GitHub template source type looks like:

azd template source add <key> --type gh --location <your-uri> --displayname <your-display-name>

Java Azure Functions support

When we introduced Java support two years ago, it started with support for ACA and App Service. Now, we’re adding Azure Functions. We’re excited to see what Java Azure Functions apps you build with this expanded support. As usual, if you build a template you’d like to share we invite you to share your work by contributing it to awesome-azd.

Alpha feature: Deployment stacks support

We’re now offering Alpha support for deployment stacks. At a high level, deployment stacks allow you to manage a group of Azure resources as a single, cohesive unit. azd provision now supports both subscription and resource group scoped deployment stacks. During azd down, deleting the deployment stack now deletes all resource groups and resources within the stack.

To enable deployment stacks, you can run:

azd config set alpha.deployment.stacks on

Since deployment stack support is considered an Alpha feature, we only recommend using it for non-business-critical scenarios.

Resource group scoped deployments promoted to beta

We’re advancing resource group scoped deployments to the beta feature stage. Promotion to beta means that the feature is documented and it has help text available in-product. It also means we confirmed via user feedback that the UX is acceptable. Still, we only recommend using this feature for non-business-critical scenarios.

Other changes and enhancements

We also added smaller enhancements and fixed issues requested by users that should improve your experience working with the azd. Some notable changes include:

Other features added to azd:

• Add visualstudio.com as valid Azure DevOps pipeline host (azure-dev#1072)
• Support for environment variable substitution for source container image (azure-dev#4124)
• Add support for args field in container.v0 and container.v1 Aspire resource types (azure-dev#4220)
• Allow GitHub pipeline providers without .zzz suffix (azure-dev#4185)

Bugs fixed in azd:

• Discrepancy in results between azd-ai-studio in GitHub workflow versus local (azure-dev#3992)
• azd up stuck on Aspire dashboard (azure-dev#4221)

New Templates

New templates this month include:

• Azure OpenAI On Your Data with Python Streamlit authored by Charlie Wei
• Blob Data Sharing with Azure Functions Flex Consumption also authored by Charlie Wei
• Pinecone Assistants Sample App authored by Pinecone Developer Relations team
• Kernel Memory authored by Kernel Memory team

Do you have an azd template you’d like to share with the rest of the community? You can learn how to with our contributor guide.

Community contributions

We’d also like to extend a special thanks to the community contributors of this release:

• Menghua Chen
  • Add note that todo-nodejs-mongo-aks app isn’t reachable (azure-dev#4235)

You can use the Azure Developer CLI from:

• Your terminal of choice on Windows, Linux, or macOS.
• Visual Studio Code or GitHub Codespaces by downloading the extension from the Marketplace, or installing it directly from the extension view (Ctrl + Shift + X for Windows or Cmd + Shift + X for macOS) in Visual Studio Code.
• Visual Studio by enabling the preview feature flag.
• You can learn more about the Azure Developer CLI from our official documentation.
• If you run into any problems or have suggestions, file an issue or start a discussion in the Azure Developer CLI repository. You can also try checking out our troubleshooting documentation.