Investigate alternative options for linkType in environment recipe schema

[kachawla]

Capturing demo feedback from sprint 2. Suggestion was that if we can find an approach that will eliminate the need for the operator to specific linkType in the environment recipe details. One of the options that came up during the discussion was using metadata with the file.

import radius as radius

resource env 'Applications.Core/environments@2022-03-15-privatepreview' = {
  name: 'recipe-test-env'
  location: 'global'
  properties: {
    compute: {
      kind: 'kubernetes'
      resourceId: 'self'
      namespace: 'demo'
    }
    providers: {
      azure: {
        scope: '/subcriptions/66d1209e-1382-45d3-99bb-650e6bf63fc0/resourceGroup/test-rg'
      }
    }
    recipes: {
      mongo: {
          linkType: 'Applications.Link/mongoDatabases' 
          templatePath: 'radiusdev.azurecr.io/recipes/mongodatabases/azure:1.0' 
      }
    }
  }
}

AB#4416

AB#10030

[rynowak]

For an example of metadata, the Bicep syntax for this looks like:

@metadata({ 'radius.connectorType': 'Applications.Connector/mongoDatabases'})

The keys and values are arbitrary, and metadata can be attached to basically anything in a Bicep file (eg: resources, parameters), including the file as a whole.

[rynowak]

I think another factor here is that we want to expose the connector type via the API. Operations like listing recipes in the CLI won't be very intuitive if we can't display the most important information.

Right now we require the user to specify the connector type, so its automatically included in the API. Any changes we make to the design need to account for us populating the same information.

[kachawla]

We have changed the schema since this was created, resource type is now a critical part of env recipe schema so this proposal is not applicable anymore. Closing.