Generate environment variables for managed secrets

Copilot-Session: 04ca0340-665a-4e7a-a907-0a0e6ea942c5
Signed-off-by: willdavsmith <willdavsmith@gmail.com>

Author: willdavsmith

.github/scripts/test-recipe.sh

@@ -48,6 +48,47 @@ ensure_workspace_context() {
     rad workspace switch "$WORKSPACE_NAME" >/dev/null 2>&1 || true
 }
 
+validate_connection_environment_variables() {
+    if [[ "$PLATFORM" != "kubernetes" ]]; then
+        return 0
+    fi
+
+    if [[ "$RESOURCE_TYPE" == "Radius.Compute/containers" ]]; then
+        echo "==> Validating direct Secret connection environment variables"
+        local deployment_json
+        deployment_json=$(kubectl get deployment myapp -n testapp -o json) || return 1
+
+        echo "$deployment_json" | jq -e '
+            (.spec.template.spec.containers[] | select(.name == "orderprocessor").env) as $app |
+            (.spec.template.spec.initContainers[] | select(.name == "dbmigration").env) as $init |
+            ($app | any(.name == "CONNECTION_SECRETS_USERNAME" and .value == "explicit-user")) and
+            ($app | any(.name == "CONNECTION_SECRETS_PASSWORD" and .valueFrom.secretKeyRef.key == "password")) and
+            ($app | any(.name == "CONNECTION_SECRETS_APIKEY" and .valueFrom.secretKeyRef.key == "apikey")) and
+            ($app | all(.name | startswith("CONNECTION_DISABLEDSECRETS_") | not)) and
+            ($init | any(.name == "CONNECTION_SECRETS_USERNAME" and .valueFrom.secretKeyRef.key == "username")) and
+            ($init | any(.name == "CONNECTION_SECRETS_PASSWORD" and .valueFrom.secretKeyRef.key == "password")) and
+            ($init | any(.name == "CONNECTION_SECRETS_APIKEY" and .valueFrom.secretKeyRef.key == "apikey")) and
+            ($init | all(.name | startswith("CONNECTION_DISABLEDSECRETS_") | not))
+        ' >/dev/null
+    elif [[ "$RESOURCE_TYPE" == "Radius.Data/redisCaches" ]]; then
+        echo "==> Validating producer managed-secret environment variables"
+        local deployment_json
+        deployment_json=$(kubectl get deployment democontainer -n testapp -o json) || return 1
+
+        echo "$deployment_json" | jq -e '
+            (.spec.template.spec.containers[] | select(.name == "demo").env) as $env |
+            ($env | any(.name == "CONNECTION_REDIS_HOST" and has("value"))) and
+            ($env | any(.name == "CONNECTION_REDIS_PORT" and has("value"))) and
+            ($env | any(
+                .name == "CONNECTION_REDIS_URL" and
+                .valueFrom.secretKeyRef.key == "url" and
+                (.valueFrom.secretKeyRef.name | length > 0)
+            )) and
+            ($env | all(.name != "CONNECTION_REDIS_SECRETS"))
+        ' >/dev/null
+    fi
+}
+
 resolve_environment_path() {
     # Resolve the full environment resource ID to avoid hardcoding the provider path
     if ! ENVIRONMENT_JSON=$(rad env show "$ENVIRONMENT_NAME" --workspace "$WORKSPACE_NAME" -o json --preview 2>/dev/null); then
@@ -180,6 +221,15 @@ fi
 # Deploy the test app
 if rad deploy "$TEST_FILE" --application "$APP_NAME" -e "$ENVIRONMENT_PATH" $PARAMS; then
     echo "==> Test deployment successful"
+
+    if ! validate_connection_environment_variables; then
+        echo "==> Connection environment variable validation failed"
+        rad app delete "$APP_NAME" --yes 2>/dev/null || true
+        kubectl delete secrets --all -n testapp 2>/dev/null || true
+        kubectl delete deployments --all -n testapp 2>/dev/null || true
+        kubectl delete services --all -n testapp 2>/dev/null || true
+        exit 1
+    fi
 
     # Cleanup: delete the app
     echo "==> Cleaning up test application"

AI/models/README.md

@@ -26,4 +26,4 @@ Recipes for this resource type are provided through the platform Recipe Packs at
 
 ## Using the resource type
 
-Add a `models` resource to your application and connect a container to it. Radius injects the model's connection properties into the container as environment variables named `CONNECTION_<CONNECTION-NAME>_<PROPERTY-NAME>` (for example `CONNECTION_LLM_MODEL` and `CONNECTION_LLM_ENDPOINT`). The `apiKey` secret is not injected — bind it from the managed `Radius.Security/secrets` resource with a container `secretKeyRef` using `model.properties.secrets.name`. See [`test/app.bicep`](test/app.bicep) for a complete example.
+Add a `models` resource to your application and connect a container to it. One connection named `llm` injects ordinary `CONNECTION_LLM_MODEL` and `CONNECTION_LLM_ENDPOINT` values plus the secret-backed `CONNECTION_LLM_APIKEY`. No second managed-Secret connection is needed. For custom Kubernetes configuration, `model.properties.secrets.name` remains available as the `secretName` for an explicitly authored `secretKeyRef`. See [`test/app.bicep`](test/app.bicep) for a complete example.

AI/models/models.yaml

@@ -46,11 +46,12 @@ types:
 
       - CONNECTION_LLM_MODEL
       - CONNECTION_LLM_ENDPOINT
+      - CONNECTION_LLM_APIKEY (secret-backed)
 
-      The `apiKey` secret is NOT injected via the connection — it is materialized
-      into a managed `Radius.Security/secrets` resource. Bind it into a container
-      env var with a `secretKeyRef`, using `model.properties.secrets.name` as the
-      `secretName` and key `apiKey` (see the `secrets` property).
+      The same connection injects `apiKey` through a Kubernetes secret reference;
+      no second managed-Secret connection is needed. For custom Kubernetes
+      configuration, use `model.properties.secrets.name` as the `secretName` and
+      `apiKey` as the key in an explicitly authored `secretKeyRef`.
 
     apiVersions:
       '2025-08-01-preview':

AI/models/test/app.bicep

@@ -27,19 +27,6 @@ resource democontainer 'Radius.Compute/containers@2025-08-01-preview' = {
     containers: {
       demo: {
         image: 'ghcr.io/radius-project/samples/demo:latest'
-        // The recipe's secret output(s) are materialized into a managed
-        // Radius.Security/secrets resource and consumed here BY REFERENCE via
-        // secretKeyRef — the value never lands on model state.
-        env: {
-          MODEL_APIKEY: {
-            valueFrom: {
-              secretKeyRef: {
-                secretName: model.properties.secrets.name
-                key: 'apiKey'
-              }
-            }
-          }
-        }
         ports: {
           web: {
             containerPort: 3000
@@ -48,6 +35,7 @@ resource democontainer 'Radius.Compute/containers@2025-08-01-preview' = {
       }
     }
     connections: {
+      // Injects model/endpoint plus secret-backed CONNECTION_LLM_APIKEY.
       llm: {
         source: model.id
       }

AI/search/README.md

@@ -25,4 +25,4 @@ Recipes for this resource type are provided through the platform Recipe Packs at
 
 ## Using the resource type
 
-Add a `search` resource to your application and connect a container to it. Radius injects the search service's connection properties into the container as environment variables named `CONNECTION_<CONNECTION-NAME>_<PROPERTY-NAME>` (for example `CONNECTION_SEARCH_ENDPOINT`). The `apiKey` secret is not injected — bind it from the managed `Radius.Security/secrets` resource with a container `secretKeyRef` using `search.properties.secrets.name`. See [`test/app.bicep`](test/app.bicep) for a complete example.
+Add a `search` resource to your application and connect a container to it. One connection named `search` injects the ordinary `CONNECTION_SEARCH_ENDPOINT` value plus the secret-backed `CONNECTION_SEARCH_APIKEY`. No second managed-Secret connection is needed. For custom Kubernetes configuration, `search.properties.secrets.name` remains available as the `secretName` for an explicitly authored `secretKeyRef`. See [`test/app.bicep`](test/app.bicep) for a complete example.

AI/search/search.yaml

@@ -46,11 +46,12 @@ types:
       example the connection name is `search` so the environment variables will be:
 
       - CONNECTION_SEARCH_ENDPOINT
+      - CONNECTION_SEARCH_APIKEY (secret-backed)
 
-      The `apiKey` secret is NOT injected via the connection — it is materialized
-      into a managed `Radius.Security/secrets` resource. Bind it into a container
-      env var with a `secretKeyRef`, using `search.properties.secrets.name` as the
-      `secretName` and key `apiKey` (see the `secrets` property).
+      The same connection injects `apiKey` through a Kubernetes secret reference;
+      no second managed-Secret connection is needed. For custom Kubernetes
+      configuration, use `search.properties.secrets.name` as the `secretName` and
+      `apiKey` as the key in an explicitly authored `secretKeyRef`.
 
     apiVersions:
       '2025-08-01-preview':

AI/search/test/app.bicep

@@ -26,19 +26,6 @@ resource democontainer 'Radius.Compute/containers@2025-08-01-preview' = {
     containers: {
       demo: {
         image: 'ghcr.io/radius-project/samples/demo:latest'
-        // The recipe's secret output(s) are materialized into a managed
-        // Radius.Security/secrets resource and consumed here BY REFERENCE via
-        // secretKeyRef — the value never lands on searchService state.
-        env: {
-          SEARCH_APIKEY: {
-            valueFrom: {
-              secretKeyRef: {
-                secretName: searchService.properties.secrets.name
-                key: 'apiKey'
-              }
-            }
-          }
-        }
         ports: {
           web: {
             containerPort: 3000
@@ -47,6 +34,7 @@ resource democontainer 'Radius.Compute/containers@2025-08-01-preview' = {
       }
     }
     connections: {
+      // Injects endpoint plus secret-backed CONNECTION_SEARCH_APIKEY.
       search: {
         source: searchService.id
       }

Compute/containers/README.md

@@ -49,6 +49,16 @@ A list of available Recipes for this Resource Type, including links to the Bicep
 | context.resource.properties.extensions | Dapr extension for Radius |
 | context.resource.properties.platformOptions | Kubernetes Deployment and Pod override properties |
 
+### Connections and secrets
+
+For ordinary connections, the Kubernetes Recipes inject `context.resource.connections.<name>.properties` as `CONNECTION_<CONNECTION-NAME>_<PROPERTY-NAME>` environment variables. When a producer Recipe returns secrets, Radius supplies reference metadata under `context.resource.connections.<name>.secrets`; the same connection injects each secret through a Kubernetes `secretKeyRef`. For example, Redis connection `redis` supplies its ordinary `host` and `port` values together with the secret-backed `CONNECTION_REDIS_URL`.
+
+Direct connections to user-authored `Radius.Security/secrets` resources remain supported and inject one secret-backed variable per data key. Both regular and init containers receive generated variables. Explicit container environment variables take precedence, managed secret references take precedence over ordinary properties with the same generated name, and `disableDefaultEnvVars: true` disables both ordinary and secret-backed variables for that connection.
+
+Connection names, property names, and secret names are uppercased when generating environment variable names. Names that collide after uppercasing are rejected. The Kubernetes Secret name is derived from the final segment of each full Radius Secret resource ID. Secret values remain in Kubernetes references and are never copied into Recipe output or plaintext container configuration.
+
+The Azure ACI Recipe is unchanged and does not consume the Kubernetes secret reference metadata described above.
+
 Note: The Azure ACI recipe does not support `context.resource.properties.extensions.daprSidecar` and ignores Dapr sidecar configuration provided through `extensions`.
 Note: The Azure ACI recipe does not support `context.resource.properties.replicas` or `context.resource.properties.autoScaling.*`; scaling is controlled by recipe-specific parameters (`desiredCount` and `maintainDesiredCount`).
 Note: The Azure ACI recipe does not support `context.resource.properties.containers.args` or `context.resource.properties.containers.workingDir`; `args` are only used by merging into the ACI `command` array, and `workingDir` is ignored.

Compute/containers/containers.yaml

@@ -89,6 +89,13 @@ types:
 
       To mount a persistent volume or secret see the PersistentVolumes and Secrets Resource Types.
 
+      On Kubernetes, each connection injects ordinary producer properties and
+      Recipe-managed secret references using
+      `CONNECTION_<CONNECTION-NAME>_<PROPERTY-NAME>`. Explicit environment variables
+      take precedence, followed by managed secret references, then ordinary values.
+      Set `disableDefaultEnvVars: true` to disable all generated variables for a
+      connection. This behavior applies to regular and init containers.
+
     apiVersions:
       '2025-08-01-preview':
         schema: 
@@ -117,7 +124,7 @@ types:
                     description: (Required) The resource ID of the resource this container is dependent upon.
                   disableDefaultEnvVars:
                     type: boolean
-                    description: (Optional) Disables the automatic injection of environment variables from connected resource properties.
+                    description: (Optional) Disables automatic injection of ordinary properties and secret-backed environment variables from this connection.
                 required: [source]
             containers:
               type: object