Skip to content

Conversation

@sk593
Copy link
Contributor

@sk593 sk593 commented Dec 10, 2025

Description

This PR adds a test workflow for Azure recipes. It uses the app.bicep under the test folder with recipes from the azure folder. There are now separate workflows for Kubernetes and Azure deployments. Azure deployments require approval from an authorized reviewer.

Related GitHub Issue:

Testing

Contributor Checklist

  • File names follow naming conventions and folder structure
  • Platform engineer documentation is in README.md
  • Developer documentation is the top-level description property
  • Example of defining the Resource Type is in the developer documentation
  • Example of using the Resource Type with a Container is in the developer documentation
  • Verified the output of rad resource-type show is correct
  • All properties in the Resource Type definition have clear descriptions
  • Enum properties have values defined in enum: []
  • Required properties are listed in required: [] for every object property (not just the top-level properties)
  • Properties about the deployed resource, such as connection strings, are defined as read-only properties and are marked as readOnly: true
  • Recipes include a results output variable with all read-only properties set
  • Environment-specific parameters, such as a vnet ID, are exposed for platform engineers to set in the Environment
  • Recipes use the Recipe context object when possible
  • Recipes are provided for at least one platform
  • Recipes handle secrets securely
  • Recipes are idempotent
  • Resource types and recipes were tested

@sk593 sk593 force-pushed the add-azure-deployments branch from e8925ff to 1c53e21 Compare December 10, 2025 21:46
@sk593 sk593 force-pushed the add-azure-deployments branch from 1c53e21 to 4ab637b Compare December 10, 2025 22:10
@sk593 sk593 force-pushed the add-azure-deployments branch from 4ab637b to 39ecf23 Compare December 10, 2025 23:00
@sk593 sk593 force-pushed the add-azure-deployments branch from 39ecf23 to 443b0b0 Compare December 10, 2025 23:31
@sk593 sk593 force-pushed the add-azure-deployments branch from fc0b2f9 to 5a5bb25 Compare December 29, 2025 20:10
@sk593 sk593 force-pushed the add-azure-deployments branch from 5a5bb25 to 853ac7d Compare December 29, 2025 21:30
@sk593 sk593 force-pushed the add-azure-deployments branch from 853ac7d to ea354e4 Compare December 29, 2025 23:30
@sk593 sk593 force-pushed the add-azure-deployments branch from ea354e4 to f3246d4 Compare December 29, 2025 23:43
Signed-off-by: sk593 <[email protected]>
Signed-off-by: sk593 <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants