This message was deleted.

Transferring resources between stacks is currently a manual task, unfortunately. We want to do some things to improve that experience. One thing we have done recently is added some validation to

pulumi stack import

to ensure that the import file is valid. Aside from that, though, it’s a matter of moving resources between stacks (you can use

pulumi stack export

and

pulumi stack import

here to help) and refactoring code to match.

ehh I am a newish pulumi user. But adding on to this, is it possible to create a project structure that prevents slamming everything into

main.go

? The project structure I am hoping for is to some how have my pulumi scripts as a module and maybe the yaml files for configuration? Possibly have:

infrastructure/
  code/[main.go, vpc.go, ec2.go]
  pulumi.yaml
  pulumi-dev.yaml

I could make a new message to avoid slamming @icy-controller-6092 request, but I can kind of see a relationship here

@quick-laptop-52657 Yes, definitely possible! You’ll need to create functions in your

vpc.go

and

ec2.go

files that accept context and pass back any properties you need to reference elsewhere, then call those functions from

main.go

. I need to hop into a meeting, but I’ll try to see if there’s an example somewhere I can point you to.

Well in my opinion this is a great example and this gives me everything I was looking for! Thank you so much ❤️

No problem, happy to help