Overview of roadmap item
Today, using a community module such as Azure verified module or a terraform Registry module as a Recipe requires writing a wrapper that adds a context input variable and structured result output, publishing the wrapper, and maintaining it separately. This creates adoption friction, maintenance burden, and locks out direct usage of production-ready community modules.
This feature is to enable platform engineers to use any standard Bicep or Terraform module directly as a Radius Recipe without writing a Radius-specific wrapper. Point location directly at a standard module source (Terraform registry, Azure Verified Modules), and the system handles input resolution (injecting Radius context via {{context.*}} expressions) and output mapping (mapping module outputs to resource properties) externally.
Related issues
Additional context
Overview of roadmap item
Today, using a community module such as Azure verified module or a terraform Registry module as a Recipe requires writing a wrapper that adds a context input variable and structured result output, publishing the wrapper, and maintaining it separately. This creates adoption friction, maintenance burden, and locks out direct usage of production-ready community modules.
This feature is to enable platform engineers to use any standard Bicep or Terraform module directly as a Radius Recipe without writing a Radius-specific wrapper. Point location directly at a standard module source (Terraform registry, Azure Verified Modules), and the system handles input resolution (injecting Radius context via {{context.*}} expressions) and output mapping (mapping module outputs to resource properties) externally.
Related issues
Additional context