This message was deleted.
# generals
sparse-intern-71089
04/07/2021, 3:57 PMThis message was deleted.
g
green-musician-49057
04/07/2021, 4:01 PMI asked a similar question last week and the recommendations were to have multiple Pulumi projects for these different modules
green-musician-49057
04/07/2021, 4:02 PMAnd from there, we're looking at using Pulumi's Automation API to loosely couple the infra projects together
b
billowy-army-68599
04/07/2021, 4:17 PM
In this particular case, I'd do the following:
- define the VPC as its own project, output the VPC id as a stack output
- encapsulate the rest of your logic into component resources with an input arg of VPC id
- you can then either 1) grab the vpc id as a stack output or 2) use
vpc.get()✨ 1
billowy-army-68599
04/07/2021, 4:17 PM
it gives you a lot of flexibility
billowy-army-68599
04/07/2021, 4:19 PM
my usual advice is to group projects together logically using considerations of "rate of change" or "blast radius" as a consideration. What I mean by that is, if you have a shared VPC for a lot of different stuff, that is likely to change a lot less than the things that live inside it, so it's useful to decouple them into different proijects
b
bumpy-summer-9075
04/07/2021, 5:05 PMMakes sense, thanks a lot @green-musician-49057 & @billowy-army-68599!
The only downside of this is that the subproject is not independant; if I were to start from scratch, but it's a very minor problem compared to the upsides
b
billowy-army-68599
04/07/2021, 5:06 PM
can you elaborate on that a little? not quite followingh
b
bumpy-summer-9075
04/07/2021, 5:31 PMLet's say I have two stacks:
commons3-websites3-websiteb
billowy-army-68599
04/07/2021, 5:33 PM
ahhh got it, yeah I'm following now
billowy-army-68599
04/07/2021, 5:34 PM
yeah that is a trade off, but I think you'll find the pros outweigh the cons 🙂
b
bumpy-summer-9075
04/07/2021, 5:34 PMFor sure! And the fact that it will break if the
commonb
billowy-army-68599
04/07/2021, 5:37 PM
you can even
throw❤️ 1
b
bumpy-summer-9075
04/07/2021, 5:39 PMdamn that's true! It's cleaner than the way I used to "throw" in TF haha:
Copy code
locals {
# Abusing the 'file' function to fail if the specified environment does not match the workspace
assert_environment_matches_workspace = terraform.workspace != var.environment ? file("ERROR: Environment needs to match the workspace") : null
}