This message was deleted.
# general
s
This message was deleted.
b
it sounds like your infrastructure might be in your functions project state, you'll need to move them if that's the case
👍 1
d
actually looking at this https://github.com/pulumi/examples/tree/master/aws-stackreference-architecture it seems like I have to create a new stack for each project, is that the case? So part of my problem might be that 'functions' is a subfolder of infrastructure? And they are in the same stack?
b
you'll need to
pulumi new
a new project and move the code into that, then migrate it out of the state
👍 1
projects hold your code, stacks are implementations of that code with config differences
g
We just completed doing something similar (and with CI/CD hooked up to boot). You'll want to import the lambda function resources over into the
functions
project once you've created it
d
@green-musician-49057 which I think it's kind of what this script does https://github.com/pulumi/pulumi/issues/3389 right
g
That's a neat script, kind of wish I had seen it earlier 😂 It would have helped us a little bit, but we also had custom providers (e.g. non-default AWS provider pointing to
us-east-1
for example). I did it mostly by hand using the pulumi cli, and it wasn't too bad b/c we only had about 20-30 resources in total across all stacks.