Azure Developer CLI Golden Path (install ➡️ local development ➡️ first deployment)

[savannahostrowski]

As part of an effort to make azd onboarding awesome, this issue aims to track various stages of the onboarding experience (let's call it the golden path; install ➡️ local development ➡️ first deployment) that might cause application developers issues and/or slow their progress getting their app to the cloud using azd.

Right now, I've grouped these issues into a couple different categories:

• Installation of azd + CLI/template dependencies
• Familiarization with azd commands/capabilities
• Make project initialization delightful
• Templates
• CLI Outputs

Each category has at least one JTBD/user story associated with it. This list of issues is dynamic so if there are other things (or categories) that you think are pain points/unnecessary friction to getting started with azd, let me know and we can figure out the best way to get it incorporated! All issues linked here have the golden-path tag on them.

A. Installation of azd + CLI/template dependencies

1. "As an application developer, I want to install the Azure Developer CLI with my package manager of choice and with minimal required dependencies, so that I can get started without having to jump around between documentation and encounter minimal dependency issues"

• Deprecate AZ CLI usage within AZD #709
• [Issue] Simplify azd installation process (dependencies) #821
• Support for package managers/installers #847

B. Familiarization with azd commands/capabilities

1. "As an application developer, I need to be able to easily familiarize myself with Azure Developer CLI capabilities after I install the tool, so that I can meaningfully use the CLI and complete my task at hand (e.g. getting my application deployed on Azure)"

• azd help improvements #822

C. Make project initialization delightful

1. "As an application developer, I want the Azure Developer CLI to provide me with an opinionated take on what cloud infrastructure I need to get my application up to the cloud, with minimal overhead, so that I don't have to do a ton of research and my productivity isn't hindered."

• As a developer, I can have azd generate all the required assets to deploy my web application with/without a database to Azure #705
• [Spike] Azd and Starshot Integration #819
• [Core] azd environment redesign - Implementation #808
  • [Issue] Increase specificity of "environment" in azd init/azd up #112
  • [Env Redesign/Impl] Default environment name to current directory name... #335
• Call azd login for the user if they invoke an azd command and are not authenticated #1391

D. Templates

1. "As a an application developer, I want to be able to easily find a template that matches my application stack, so that I can quickly get started on Azure and be set up for success from day 1"
2. "As an application developer, I want to know that a template I choose with work with the latest version of the Azure Developer CLI, so that I know that I am setting my application up with best practices and securely on Azure"

• Template Discoverability + Contribution #418
  • Scenario "Blue Badge Samples" - As a dev, I want to be able to easily recognize when a sample I found in the Azure samples browser will work with azd #425
  • Discuss template/CLI backwards compatibility #287
• Design exploration for template discoverability #637
• azd up should display warning message when downloading a non-Azure-Samples template #273

E. CLI outputs

1. "As an application developer, I need to be able to recover from errors that I encounter when using the Azure Developer CLI, so that I can get my application's infrastructure provision and my app deployed on Azure"
2. "As an application developer, I need to be able to clearly understand what is being provisioned/deployed for me on Azure, so that I can the cloud components of my application, understand how my application is mapped out in the Azure Portal + learn the fundamentals

• UX Explorations: Common Error States #243
• Investigate UX improvements to the azd up provisioning flow #255
• Include a summary or completion message after down #508