Error when switching Recipes from dev to azure

[AaronCrawfis]

Steps to reproduce

1. Run rad init --dev and create a new application
2. Replace the contents of app.bicep with:

import radius as radius

@description('The ID of your Radius environment. Automatically injected by the rad CLI.')
param environment string

@description('The ID of your Radius application. Automatically injected by the rad CLI.')
param application string

resource frontend 'Applications.Core/containers@2022-03-15-privatepreview' = {
  name: 'frontend'
  properties: {
    application: application
    container: {
      image: 'radius.azurecr.io/tutorial/webapp:edge'
    }
    connections: {
      // Define a connection to the redis container
      // Automatically injects conneciton information into the container
      redis: {
        source: db.id
      }
    }
  }
}

resource db 'Applications.Link/redisCaches@2022-03-15-privatepreview' = {
  name: 'db'
  properties: {
    environment: environment
    application: application
    // recipe is not specified, so it uses 'default' if present
  }
}

3. Run rad deploy. It should succeed
4. Run:

   rad recipe register azure --environment default --template-kind bicep --template-path radius.azurecr.io/recipes/azure/rediscaches:0.21 --link-type Applications.Link/redisCaches

5. Update your app.bicep with:

import radius as radius

@description('The ID of your Radius environment. Automatically injected by the rad CLI.')
param environment string

@description('The ID of your Radius application. Automatically injected by the rad CLI.')
param application string

resource frontend 'Applications.Core/containers@2022-03-15-privatepreview' = {
  name: 'frontend'
  properties: {
    application: application
    container: {
      image: 'radius.azurecr.io/tutorial/webapp:edge'
    }
    connections: {
      // Define a connection to the redis container
      // Automatically injects conneciton information into the container
      redis: {
        source: db.id
      }
    }
  }
}

resource db 'Applications.Link/redisCaches@2022-03-15-privatepreview' = {
  name: 'db'
  properties: {
    environment: environment
    application: application
    recipe: {
      // Name a specific recipe to use
      name: 'azure'
    }
  }
}

6. Deploy with rad deploy
7. Get error

Observed behavior

$ rad deploy .\app.bicep
Building .\app.bicep...
Deploying template '.\app.bicep' for application 'recipes' and environment 'default' from workspace 'default'...

Deployment In Progress...

Failed               db              Applications.Link/redisCaches
Error: {
  "code": "DeploymentFailed",
  "message": "At least one resource deployment operation failed. Please see the details for the specific operation that failed.",
  "details": [
    {
      "code": "ResourceDeploymentFailure",
      "message": "Failed",
      "details": [
        {
          "code": "Internal",
          "message": "failed to delete resource \"/planes/kubernetes/local/namespaces/default-recipes/providers/core/Service/redis-ymbjcqyjzwkpg\": resource name may not be empty"
        }
      ]
    }
  ]
}

TraceId:  2d21d7295cbe32be5536d283be1b7569

Expected results

I would expect the Kubernetes service deletion to succeed and the deployment to succeed

Workaround

Run rad resource delete rediscaches db to delete the redis cache (and the resources within the recipe)

Version

RELEASE   VERSION   BICEP     COMMIT
0.21.1    v0.21.1   0.11.51   5e152fe79ad50d179a1339ae10c7d0a6e4e20686

AB#8135

[rynowak]

Note that this is something we'll block in the future (recipe stickiness).

However this is a real bug, and a good way for us to test garbage collection for recipes. We should fix this and add a functional test for garbage collection.