Overview of the Resource type and Recipe
The expectation for stable Recipes in this repository is that they'll work with a single unified app.bicep even if the underlying platform is different (i.e. a Kubernetes Recipe and Azure Recipe for containers should both work with the same app.bicep)
Acceptance criteria
We should add documentation explaining this criteria if an app.bicep is present in the resource type folder (this will be true for stable resources as they'd be part of Radius)
Additional context
No response
Would you like to support us?
AB#17996