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.

Pulumi Community

image.png

I'm making some plans to use pulumi to manage infrastructure on edge devices. I'm wondering what the typical pattern is for managing a pulumi program for multiple target systems. The docs frequently refer to different environments like dev, prod, etc. Is it sensible to use the stack concept to map to a particular system? Something like the attached image.

I suppose this isn't unlike using different kubernetes namespaces as deployment configuration.

Although in my case the targets are distinct physical systems.

Are there any concerns with concurrency if I tried applying multiple stacks simultaneously assuming they all use the same pulumi backend location?

My main concern there would be corrupting stack state.

This is the correct pattern. There's no issues using multiple stacks at the same time, each stack has its own state file.

At the state / infra levels, projects don't really exist, only stacks do. Projects are pretty much just at the code level.