Open savannahostrowski opened 1 year ago
Currently, we manage and configure our internal dependencies i.e., Bicep CLI and GitHub CLI. Managing and configuring external runtimes, tools and dependencies feels too big of a scope for Dilithium. Moving to backlog.
cc @ellismg @kristenwomack
The WinGet team recently released WinGet configuration, which is configuration as code that can help Windows developers with machine setup and project onboarding. With WinGet configuration, a developer can check configuration as code into their project that details the dependencies/versions/etc. and then when new developers onboard to their project, they can run
winget configure
in their development environment to install all of the relevant runtimes/tools for the project.While we (the
azd
team) have spent a lot of time driving down the number of dependencies required for a developer to get started with theazd
binary, there is still opportunity for us to help streamline the getting started experience of templates/azd-compatible codebases.We should explore having some of our core commands look for WinGet configuration (perhaps in infra/) in azd-compatible projects and add logic to
azd
to runwinget configure
under the hood, when applicable. Some ideas here might be to investigate how we could include such logic into:azd restore
- to restore all app dependencies.azd init
- when the user first pulls the project down and initializes the applicationWe could would also want to include WinGet configurations in the templates we author for easier onboarding.