[EPIC] Unified Infrastructure Extensibility: CDK, Aspire, and Custom Provisioning Providers

[jongio]

Overview

Umbrella spec tying together the infrastructure extensibility work across CDK language support, Aspire polyglot integration, and custom provisioning providers into one cohesive design. The goal is a unified architecture where developers can define infrastructure in any language (C#, TypeScript, Python, Go) and have all azd commands work transparently -- whether through CDK, Aspire AppHost, or custom provisioning extensions.

Detailed spec in progress.

Related Issues

Provisioning Provider Extensibility

• Provisioning Provider Extensibility #6231 - Provisioning Provider Extensibility (feature request)
• Epic: Provisioning Providers in the AZD Extension Framework #7465 - Epic: Provisioning Providers in the AZD Extension Framework (implementation epic with 16 sub-issues)

CDK Language Support

• Feature: CDK Language Support — Author Azure Infrastructure in Any Programming Language #7425 - Feature: CDK Language Support -- Author Azure Infrastructure in Any Programming Language (spec + POC PR feat: add dotnet infrastructure provisioning provider (Azure.Provisioning) #7352)

Aspire Integration

• Support Aspire polyglot (non-C#) AppHost projects in azd #7138 - Support Aspire polyglot (non-C#) AppHost projects in azd

Service Discoverability

• Custom Service Discoverability #6229 - Custom Service Discoverability
• Resource Discoverability #6230 - Resource Discoverability

Key Design Questions

1. Core provider vs extension for CDK languages
2. Single CDK extension vs per-language extensions
3. How Aspire polyglot detection integrates with the provisioning provider framework
4. azd init UX for selecting infrastructure language
5. Template ecosystem support for multiple IaC languages