The base stack uses a component that defines an RDS instance, and I export the db address in the following way:

const adHocBaseEnv = new AdHocBaseEnvComponent('myAdHocBaseEnv', {
  certificateArn: process.env.CERTIFICATE_ARN,
  domainName: process.env.DOMAIN_NAME
});

export const rdsAddress = adHocBaseEnv.databaseInstance.address;

In the Pulumi console I can see that the RDS address is showing up correctly. 👍

In the app stack I use the rds address (and other values taken from the base stack) in the following way:

const org = process.env.PULUMI_ORG;
const environment = process.env.PULUMI_ENVIRONMENT;

const stackReference = new pulumi.StackReference(`${org}/ad-hoc-base/${environment}`)

// ...
const rdsAddress = stackReference.getOutput("rdsAddress") as pulumi.Output<string>;

// ad hoc app env
const adHocAppComponent = new AdHocAppComponent("AdHocAppComponent", {
  // ...
  rdsAddress,
});

In the app stack I define a variable called

envVars

with values that I want to pass to containers in the ECS task definitions like this:

const envVars: { [key: string]: pulumi.Output<string> | string }[] = [
      {
        name: "POSTGRES_SERVICE_HOST",
        value: pulumi.interpolate `${props.rdsAddress}`,
      },
      // ...
    ];

I’m not sure if the type I have selected here for

envVars

is correct, but it doesn’t throw any errors in my editor.

I then pass the

envVars

value to components that define taskDefinitions, like this:

const apiService = new WebEcsService("ApiWebService", {
      name: "gunicorn",
      command: ["gunicorn", "-t", "1000", "-b", "0.0.0.0:8000", "--log-level", "info", "backend.wsgi"],
      envVars,
      // ...
    });

In this component I define taskDefinitions:

const taskDefinition = new aws.ecs.TaskDefinition(`${props.name}TaskDefinition`, {
      containerDefinitions: JSON.stringify([
        {
          name: props.name,
          image: props.image,
          command: props.command,
          environment: props.envVars,
          // ...

On the component I define

envVars

in the interface like this:

envVars?: { [key: string]: pulumi.Input<string> | string }[];

This has been tricky to debug, but I imagine that it is a common pattern in apps that use ECS. Does anyone have pointers for how I can resolve this issue? 🙏

Here’s the part of my code where I define `envVars`: https://github.com/briancaffey/pulumi-aws-django/blob/main/src/components/ad-hoc/app/index.ts#L91-L124

The container is otherwise starting correctly and passing health checks, and the target group is healthy. I guess that since the environments key in the containerDefinition is being `JSON.stringify`ed, it is trying to convert values to json. I have tried to do what it suggested with

.apply(x => x.toJSON())

without any luck

Here’s what I’m seeing in containerDefintions:

I’m not sure how to use the jsonStringify method mentioned above

I found this SO thread that might be helpful: https://stackoverflow.com/questions/65970321/how-to-add-entries-to-pulumi-output-for-environment-variables

and this example: https://github.com/pulumi/examples/blob/master/aws-ts-airflow/index.ts#L61

@dry-keyboard-94795, I got it working using pulumi.jsonStringify instead of JSON.stringify, thank you for the suggestion