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

Hey, wanna know what is the best way to have config file by environment like `stage` and `prod` ?

<@UH7UWDRC6> you mean, beyond `pulumi config set ...`?

Have you created a stack for each environment?

yeah, i would like to have one stack for deploying es service in aws but i have 3 different environment how should i do it?

`"best"` way :slightly_smiling_face:, i’m starting with pulumi so i’m trying to do a poc my company

You would create one Pulumi project with 3 stacks, one for each environment

ok, do you have one example on github or somewhere? I could use the same file for creating my service?

This might be a good start
<https://pulumi.io/reference/organizing-stacks-projects.html>

But this will explain what a stack is
<https://pulumi.io/reference/stack.html>

awesome thank you sir :slightly_smiling_face:

yeah, that’s one way to do it. someday I think we’ll have facilities that let you do things like diff between environments. but stacks are the way to go for now.

all right!! What is the way to debug a `up`. with the `preview` command?

`preview` tells you what’s going to happen.

debug what i have in my `index.ts` :grimacing:

That could mean a whole bunch of things, though

`preview` is basically a dry run. Is that not enough information?