This message was deleted.

sparse-intern-71089

10/17/2022, 2:34 PM

This message was deleted.

fast-river-57630

10/17/2022, 2:38 PM

What's your backend? On the hosted one each isolated "project" could have its own "dev". I had issues doing the same with the S3 backend.

most-mouse-38002

10/17/2022, 2:46 PM

I guess right now, local, but I assume the same problem will occur on Azure blobs (which is kinda S3), unless we create different blobs for each project.

fast-river-57630

10/17/2022, 2:56 PM

yeah I'm not a pro but it was finicky for me. i ended up just using different stack names like 'project-$name' then splitting out $name when i needed it. even with 'dev' on multiple projects the stack itself isn't shared, just the name. if you want project data from one 'dev' to go to another 'dev' you need to use an output and a StackReference. https://www.pulumi.com/registry/packages/aws/how-to-guides/aws-ts-stackreference/

fast-river-57630

10/17/2022, 2:58 PM

(I assumed you were just interested in sharing the name between multiple projects but maybe you wanted to share stack data too?)

most-mouse-38002

10/18/2022, 2:08 PM

yeah, i wanted both, thanks for the tip (and sorry for late response) 👍

Open in Slack

Previous Next

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.