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

Pulumi isn't the right tool to run stuff in your VMs. Pulumi is for creating the VMs, configuring their boot instructions, and things like that.

Oh. I’m not running anything using Pulumi. I’m using another library meant to run remote commands for that. I’m more specifically talking about the stack part. Should I create a new stack for each experiment or is there a way I can call pulumi up twice and not have the stack destroy the previous resources?

Ah right. That's the right way to do it using "vanilla" Pulumi. You can get much fancier than that with automation-api.

You can, for example, dynamically create stacks and choose at run time whether to refresh/re-up an existing stack, or create a new stack.

Ah. Okay. That answers my question. Thank you very much! :slightly_smiling_face:

You could also use a single stack and dynamically add resources to it (in loops / conditionals), but the automation-api solution is better.

Yes. The automation-api is what I’m using right now.

Once you wrap it in a handy self-serve web page, and associate an experiment name with a stack, then you'll stop worrying about stacks and learn to love the ~bomb~ automation.

I’m already loving it. :slightly_smiling_face: