@echoing-match-29901 Hi team, I’m trying to understand how dynamic stack config works with Pulumi Cloud. I have a monorepo setup with separate env folders (like

stage/

), each containing its own

Pulumi.yaml

and

index.ts

. Project name is

infra

. In GitHub Actions, I build/push ECS images and run:

pulumi config set api2ImageTag <image-tag>
pulumi up

In my Pulumi code:

const config = new pulumi.Config();
const imageTag = config.get("api2ImageTag") || "latest";

I can see

infra:api2ImageTag

in Pulumi Cloud UI after deployment, but when I run:

pulumi config

locally, it only shows the vars already defined in my local

Pulumi.yaml

files and does not fetch

api2ImageTag

from Pulumi Cloud. Because of that,

config.get("api2ImageTag")

returns undefined and preview tries to revert the ECS image back to

latest

. Is there a way to make

pulumi config

/

new pulumi.Config().get()

fetch these dynamically added config values directly from Pulumi Cloud ?

I think your looking for

pulumi config refresh

which fetches the config values used from the last deployment and updates the local file with them.

I tried this command. It creates a new

pulumi.env.yaml

file and does not add it to existing

Pulumi.yaml

file. Also, how do I achieve the same outcome when I run deployments from pulumi cloud

config is generally 'per-stack' not 'per-project' so that's expected

Okay, thank you for your help

I have a monorepo setup with separate env folders (like stage/), each containing its own Pulumi.yaml and index.ts. Project name is infra.

This sounds like the source of the problem. If you have one Pulumi project, then you have one Pulumi.yaml file. If the folders contain different index.ts files, then you have different projects.