All portable resource types and examples have fully-implemented Terraform configurations

Overview of roadmap item

The majority of Radius users use Terraform as their IaC solution. Radius today is biased towards Bicep. This roadmap item includes:

1. Implementing Terraform configurations for all portable resource types in the recipes repo for AWS, Azure, and local development
2. Modifying rad init to ask the user whether to use Terraform or Bicep recipes
3. Rewriting the Terraform recipe overview documentation to explain in detail how to author a Terraform recipe including:
   • What module storage options Radius supports (generic Git)
   • How to reference a Terraform configuration when registering a recipe (git::https://github.com//.git//directory/sub-directory
   • What Terraform backend options Radius supports (Kubernetes)
   • Other technical detail for Terraform practitioners

Related issues

• https://github.com/radius-project/radius/issues/9224
• https://github.com/radius-project/radius/issues/9225
• https://github.com/radius-project/radius/issues/9226

Start by reviewing the linked recipes repository and related issues 9224, 9225, and 9226 to understand the remaining scope. The roadmap item is complete when portable resource types have Terraform configurations for AWS, Azure, and local development, rad init supports choosing Terraform or Bicep recipes, and the Terraform recipe overview documents authoring, storage, registration, and backend options.