radius-golden-path-builder

Build Azure golden paths with Radius Resource Types, Dapr, and Bicep Recipes.

Updated Jul 16, 2026
One-click install
npx skills add https://github.com/Cloud-Byte-Consulting/plugins --skill radius-golden-path-builder-cloud-byte-consulting
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: radius-golden-path-builder
Source: https://github.com/Cloud-Byte-Consulting/plugins/tree/main/azure-platform-engineering/skills/radius-golden-path-builder
Command: npx skills add https://github.com/Cloud-Byte-Consulting/plugins --skill radius-golden-path-builder-cloud-byte-consulting

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Platform teams need a repeatable way to stamp out Azure golden paths that keep application code portable across compute targets and backing stores, without hand-writing infrastructure for every environment. ## Core Features & Use Cases - Golden path stamping: Generates Radius Resource Types, per-environment Bicep Recipes (dev k8s, Azure Container Apps, AKS), APIM route recipes, landing-zone foundation, and Flux GitOps layout from the azure-agentic-idp reference templates. - Interchangeable backends: Keeps one app.bicep portable by routing state through the Dapr state API (Redis, Cosmos DB, PostgreSQL) and compute through recipe outputs, so environment choice decides infrastructure. - Deterministic module resolution: Resolves Azure Verified Modules pins via registry tag queries and enforces recipe output contracts (host/port/baseUrl) as API. - Use Case: An org wants a golden path where the same app definition deploys to k8s in dev and AKS with PostgreSQL in production; use this Skill to stamp the types, recipes, environments, and Flux layout, then verify with iac-guardrail-verifier. ## Quick Start Ask the agent to stamp a Radius golden path for your org from the azure-agentic-idp reference templates with dev and AKS environments.

Frequently Asked Questions about radius-golden-path-builder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build a golden path on Azure with Radius?

Stamp the azure-agentic-idp reference templates: define abstract Resource Types, add per-environment Bicep Recipes for dev k8s, Container Apps, or AKS, then wire the landing zone and Flux GitOps layout. Resolve AVM module pins from the registry, never from memory.

How do Radius Recipes swap backends without changing app code?

The app only depends on the Dapr state API and an HTTP baseUrl, never a native SDK. Each environment's recipe provisions a different store (Redis, Cosmos DB, PostgreSQL) and returns host, port, and baseUrl outputs that flow to the app at deploy time.

Can Radius deploy to Azure Container Apps directly?

ACA is not a Radius compute target; the ACA flavor is provisioned by a recipe instead. This is why the abstract-type design keeps one portable app.bicep across all environments.

What are the limitations of Radius for production platforms?

Radius is CNCF Sandbox v0.x, its control plane requires Kubernetes even when targeting ACI or ACA, and Flux is the only supported GitOps engine. Durable Dapr workflows need AKS because the workflow SDK is unsupported on Container Apps.

Why does my golden path break when a workload imports a native SDK?

Importing a backing store's native SDK bypasses the Dapr building-block API, which silently breaks code portability across recipes. Keep recipe result.values contracts stable and route all state, pub-sub, and secrets through Dapr.