Add Azure recipe for the Radius.Data/mySqlDatabases resource type

[andrewmatveychuk]

Description

• Added the Azure recipe to provision the resource as an Azure Database for MySQL
• Added the new type property (tags), as suggested here, and defined the new type version for backward compatibility

Related PR: #46

Testing

From the repository root folder:

1. Create the type: rad resource-type create -f '.\Data\mySqlDatabases\mySqlDatabases.yaml'
2. Compile the Bicep extension: rad bicep publish-extension -f '.\Data\mySqlDatabases\mySqlDatabases.yaml' --target '.\Data\mySqlDatabases\radiusResources.tgz'
3. Add the compiled radiusResources.tgz file to your bicepconfig.json file to enable IntelliSense support in VSCode.
4. Publish the recipe to a container registry. For example: rad bicep publish --file '.\Data\mySqlDatabases\recipes\azure-database-for-mysql\bicep\azure-database-for-mysql.bicep' --target 'br:ghcr.io/andrewmatveychuk/azure-database-for-mysql:0.54'
5. Register the recipe in your Radius environment. For example: rad recipe register default --environment default --resource-type 'Radius.Data/mySqlDatabases' --template-kind bicep --template-path 'ghcr.io/andrewmatveychuk/kubernetes-mysql:0.54'
6. Configure the Azure provider for the environment as described here:
   • The resource group used by the Azure provider should exist.
   • The configured identity should be granted the Contributor role for the target resource group.
7. Define a sample application using the type, deploy it, and check for resource provisioning in the target resource group. For example:

extension radius
extension radiusResources

@description('The Radius Application ID. Injected automatically by the rad CLI.')
param application string

@description('The env ID of your Radius Environment. Set automatically by the rad CLI.')
param environment string

resource mysql84 'Radius.Data/mySqlDatabases@2025-08-01-preview' = {
  name: 'mysql84'
  properties: {
    environment: environment
    application: application
    database: 'wp_db84'
    username: 'wp_user84'
    version: '8.4'
  }
}

var tags = {
  environment: 'production'
  owner: 'team-b'
}

resource mysql80 'Radius.Data/mySqlDatabases@2025-10-01-preview' = {
  name: 'mysql80'
  properties: {
    environment: environment
    application: application
    database: 'wp_db80'
    username: 'wp_user80'
    version: '8.0'
    tags: tags
  }
}

resource mysql57 'Radius.Data/mySqlDatabases@2025-10-01-preview' = {
  name: 'mysql57'
  properties: {
    environment: environment
    application: application
    database: 'wp_db57'
    username: 'wp_user57'
    version: '5.7'
    tags: {
      'custom-environment': 'test'
      'custom-owner': 'team-a'
    }
  }
}

[andrewmatveychuk]

@Reshrahim @zachcasper Could you please review and let me know your thoughts?

[andrewmatveychuk]

The PR to update the documentation for the Azure provider with missing details: radius-project/docs#1539

[Reshrahim]

Thanks for the contribution.

I made some suggestions as I manually tested the Azure Recipe. I was able to deploy but the env variables did not get populated on the container via connections.

[andrewmatveychuk]

Thanks for the contribution.

I made some suggestions as I manually tested the Azure Recipe. I was able to deploy but the env variables did not get populated on the container via connections.

FYI, I'm still looking into this, and I'm trying to accomodate the TLS enforcement into the recipe.

[andrewmatveychuk]

Thanks for the contribution.

I made some suggestions as I manually tested the Azure Recipe. I was able to deploy but the env variables did not get populated on the container via connections.

@Reshrahim
I think that should work correctly now. It turned out that the databasePort property can only be used as an input parameter and cannot be referenced later, which resulted in an error when deploying the recipe Bicep template directly, rather than via Radius.

[Reshrahim]

@andrewmatveychuk - Can you review https://github.com/radius-project/resource-types-contrib/pull/95/changes#diff-efca8759f11a6cd43d11b7c4f5948402d7d743097b2f08ed6a970d897bfbb618 as a pattern for modeling secrets and start updating the mysql type. This will be published as the guidance on modeling secrets with types once the core types (extensible) are added to the Radius install