Automatically validate resource types and recipes against recent edge Radius builds

[brooke-hamilton]

Overview

Propose adding scheduled automatic runs of the validate-resource-types workflow, using the edge version of Radius, to test all resource types and recipes in this repository against changes made to Radius in the past 24 hours. This will proactively catch breaking changes from upstream Radius and help ensure continued compatibility and reliability for contributors and users.

No changes are required to the validate resource types workflow because by default it runs using the edge version of Radius and the main branch of this repo.

Acceptance criteria

• Set up a scheduled GitHub Action to trigger the validate-resource-types workflow using the edge version of Radius (e.g. nightly or every 24 hours).
• The workflow should fetch the latest edge release of Radius from the past 24 hours and execute the full resource type validation (including both bicep and terraform recipes). This is the default mode for the workflow, so no special logic needs to be added.
• A GitHub issue should be created upon failure, tagged as a "test-failure"

Additional context

This feature will increase early detection of breaking changes due to rapid development in upstream Radius. Ensuring compatibility through automated regular validation will increase trust and stability in this repository’s recipes and resource types.

Reference: Existing validate-resource-types workflow (.github/workflows/validate-resource-types.yaml).

Would you like to support us?

• Yes, I would like to support you

AB#17992