This message was deleted.
# generals
sparse-intern-71089
03/03/2021, 5:59 AMThis message was deleted.
d
damp-school-17708
03/03/2021, 11:10 AMInteresting question, I have a similar / related one.
How do people structure their pulumi code?
I am opting for monorepo, at least for broad services, and I am doing
/frontend (I'll put react.js here)
/functions (I'll put lambdas)
/infrastructure (pulumi code)
I want to split various bits, such as dynamo, etc
The only way I've seen is to do export const but that gets tedious very quickly.
How do you do it?
damp-school-17708
03/03/2021, 2:59 PM@limited-caravan-48625 I found this https://github.com/webiny/webiny-js/tree/393bf729888a077f6ffeac17d28524341da38251/packages/cwp-template-aws/template/api/pulumi/dev which looks pretty awesome HTH
🙏 1
🙌 1
b
billowy-army-68599
03/03/2021, 5:11 PM
we aren't prescriptive here, it largely depends on your needs. Having a mono repo is very common with our users
@damp-school-17708 you can use stack references to help organize things as well: https://www.pulumi.com/docs/intro/concepts/stack/#stackreferences
But you'll still need to export variables
👍 1
c
clever-cartoon-41433
03/03/2021, 7:30 PMThis is a based setup, what I used with terraform before starting the current migration to pulumi, and I fully endorse it
clever-cartoon-41433
03/03/2021, 7:31 PM1 branch = 1 env
clever-cartoon-41433
03/03/2021, 7:31 PMKeep your infrastructure changes, db migrations, and code in the same place. That way you can modify all three at the same time.