[layers v2] Rework `azd add` to land AVMs under infra instead of resources
- Dominant language
- Go
- Stars
- 569
- Forks
- 364
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 136
Description
Part of #9765.
Once we get support for layered provisioning v1.5's format, we can change `azd add` so AVM-backed resources are written into `infra` (as a layer) rather than into the legacy `resources:` model, which was unfortunately not compatible with `infra`.
As part of this we can remove the `resources:` code — this would be a complete replacement, now using layered provisioning. `resources:` was never shipped as GA, so this should have a small impact. We can verify that with telemetry, if need be.
Contributor guide
Research direction
Start with the `azd add` command and trace how AVM-backed resources are written to the legacy `resources:` model. Review the layered provisioning v1.5 work from #9765 and telemetry for `resources:` usage; done means AVM-backed resources land under `infra` as a layer and the obsolete `resources:` code is removed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, go
- Domain
- cli, cloud, infrastructure
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100