Remove CONNECTION_*_RECIPE environment variable on containers

[zachcasper]

Steps to reproduce

If a container has a connection to another resource, a PostgreSQL database for example, environment variables are automatically created for each property. For the PostgreSQL resource, these environment variables are created:

CONNECTION_POSTGRESQL_DATABASE
CONNECTION_POSTGRESQL_HOST
CONNECTION_POSTGRESQL_PASSWORD*
CONNECTION_POSTGRESQL_PORT
CONNECTION_POSTGRESQL_RECIPE
CONNECTION_POSTGRESQL_SIZE
CONNECTION_POSTGRESQL_USERNAME*

• Removed in [On hold] Refactored postgreSqlDatabases to handle secrets properly resource-types-contrib#78

All of the environment variables above are properties in the resource type definition except Recipe. Recipe is not developer-relevant and should be removed.

Observed behavior

No response

Desired behavior

CONNECTION_POSTGRESQL_RECIPE should not be an environment variable.

Workaround

No response

rad Version

0.53

Operating system

No response

Additional context

No response

AB#17800

[radius-triage-bot]

👋 @zachcasper Thanks for filing this bug report.

A project maintainer will review this report and get back to you soon. If you'd like immediate help troubleshooting, please visit our Discord server.

For more information on our triage process please visit our triage overview

[nithyatsu]

When we discussed connections design (https://github.com/radius-project/design-notes/blob/main/features/2025-02-user-defined-resource-type-feature-spec.md#scenario-3--connections) , the decision was to inject every property of the connected resource as environment variable, with out worrying about what would be relevant, the reasoning being there is not much to lose and the developer will be able to make use of any variable that is relevant. If we fix this, there might be more variables in another context that would look irelevant. Are we trying to revisit the design decision?

[zachcasper]

the decision was to inject every property of the connected resource as environment variable

I agree with this, but Recipe is not a property of the Resource Type.

there might be more variables in another context that would look irelevant. Are we trying to revisit the design decision?

Are you saying there may be other environment variables created that do not correlate to a property on the resource type? I'm only expecting environment variables to be created for actual properties that have been defined in the resource type schema.

[nithyatsu]

ables created that do not correlate to a property on the resource type? I'm only expecting environment variables to be created for actual properties that have

recipe is a property we internally add to resources deployed using recipes along with status. a sample json when we do a rad resource show looks like below.

Notice the recipe field right after provisioningState.

{
  "id": "/planes/radius/local/resourcegroups/default/providers/Radius.Resources/feedbackAI/feedbackai1",
  "location": "global",
  "name": "feedbackai1",
  "properties": {
    "application": "/planes/radius/local/resourcegroups/default/providers/Applications.Core/applications/todolist",
    "environment": "/planes/radius/local/resourcegroups/default/providers/Applications.Core/environments/aws",
    "model": "anthropic.claude-3-sonnet-20240229-v1:0",
    "provisioningState": "Succeeded",
    **"recipe": {
      "name": "default",
      "recipeStatus": "success"
    },**
    "region": "us-west-2",
    "status": {
      "computedValues": {
        "access_key_id": "notshown",
        "model": "anthropic.claude-3-sonnet-20240229-v1:0",
        "region": "us-west-2",
        "secret_access_key": "notshown"
      },
      "outputResources": [
        {
          "id": "/planes/aws/aws/accounts/179022619019/providers/AWS.iam/policy/BedrockUserPolicy-b1cfe7a8",
          "localID": "",
          "radiusManaged": true
        },
        {
          "id": "/planes/aws/aws/accounts/179022619019/providers/AWS.iam/user/bedrock-user-b1cfe7a8",
          "localID": "",
          "radiusManaged": true
        }
      ],
      "recipe": {
        "templateKind": "terraform",
        "templatePath": "git::https://github.com/reshrahim/todoapp-ai.git//recipes/aws-bedrock"
      }
    }
  },
  "type": "Radius.Resources/feedbackAI"
}

[zachcasper]

We agreed that Applications.Core/containers would not be modified.

Radius.Compute/containers will be modified to fix this issue via #10914

[radius-triage-bot]

👍 We've reviewed this issue and have agreed to add it to our backlog. Please subscribe to this issue for notifications, we'll provide updates when we pick it up.

We also welcome community contributions! If you would like to pick this item up sooner and submit a pull request, please visit our contribution guidelines and assign this to yourself by commenting "/assign" on this issue.

For more information on our triage process please visit our triage overview

[willdavsmith]

Will be fixed by radius-project/resource-types-contrib#83