As a developer, I can have azd generate all the required assets to deploy my web application with/without a database to Azure

[savannahostrowski]

v1 goal: Fingerprint JavaScript/Python web apps with/without Mongo/PostgreSQL databases, hosted on ACA w. Buildpacks

Right now, we sort of leave the exercise of figuring out what services are needed to move an app to Azure up to the developer. We should be able to provide them with more of an opinionated take so that we can decrease the cognitive load. We should also do this in approachable, non-Azure language so that folks without deep background can get started.

User flow:

• Run azd init in a codebase dir (non-templatized)
• User is provided with a series of prompts to walkthrough and accept the "suggested" services needed to move their app to the cloud (e.g. azd sees React and so we suggest Static Web Apps), with smart defaults + configurations
• At each prompt, user is provided with the opportunity to either accept the default suggestion or amend an azd-suggested service and choose another option (maybe I don't want Cosmos and actually want Azure SQL)
• As a result of the command executing, the user receives all the appropriate IaC assets in their project written in Bicep to run azd up with little to no amendments

We will evaluate both an AI and non-AI powered version of this.

Important Links

Design Artifacts

• Golden Path Flow Prototype [Figma]

Tasks

Beta Give feedback

1. Application Fingerprinting UXR #1907
   user-study +1
   
2. Application Fingerprinting: Usability Testing UX Work #1594
   design +1
   
3. [fingerprint] - Onboard to Azure ExP #1260
   feature telemetry +2
   
4. Prototype non-AI variant
5. Create initial design explorations for the Golden Path scenario [Austin A]
6. Create initial design explorations for Error and Troubleshooting scenarios [Austin A] [Jul 12 - 26]

[wbreza]

In addition to forming an opinionated infrastructure folder we should also explore generating default github actions / azdo pipeline files to help enable pipeline configuration as mentioned in #1420

[rajeshkamal5050]

@savannahostrowski @ellismg Not in scope for GA. Moving this to Gallium.

[weikanglim]

With fingerprinting, we may be able to add a subsequent feature. as @vhvb1989 suggests here:

services:
  web:
    project: ./src/web
    language: auto # may be omitted

Detecting the project file based on the folder would be fairly trivial. If we can't, we can simply emit an error.

[Austinauth]

07/07/2023 | End of week design update

This week

• Created initial Application Fingerprinting golden path prototype in Figma
• Reviewed prototype with @savannahostrowski
• Reviewed prototype with design team during crit and captured feedback

Next week

• Present Golden Path scenario prototype during team demo time (cc: @rajeshkamal5050)
• Incorporate feedback from design crit and team demo
• Create initial flow explorations for language detection failure and DB config [See blocker below]

Blockers

• Unable to create designs for the incorrect language detection, DB configuration, and other edge-case scenarios until we have a better understanding of how the language detection will work and how accurate it will be (cc: @weikanglim)

Team, feel free to comment here or in the prototype linked above if you have feedback, thoughts, or concerns

[savannahostrowski]

Other scenarios to prioritize for Ignite:

• Support for Dockerfiles - today, we are leveraging buildpacks when targeting ACA. We should also allow a developer to define their own Dockerfile
• Managed add-ons - Running Redis in a container on ACA is faster to provision. We should lean on managed add-ons where possible

[savannahostrowski]

Closing this for now in favour of smaller items. Will discuss with @weikanglim