This message was deleted.
# generals
sparse-intern-71089
08/07/2023, 11:08 PMThis message was deleted.
l
little-cartoon-10569
08/08/2023, 12:20 AMThe project name is unimportant in the decision: go with something informative. app1, app2 is probably good enough. Or if you want to deploy apps together, you might use a single apps project. You'll almost certainly need one or more base projects that the app projects depend on, to set up things like DNS, VPCs, VPC endpoints, maybe shared DBs and/or LBs, and more.
little-cartoon-10569
08/08/2023, 12:21 AMI believe that the stack name, unfortunately, needs to echo the project name in some way. This may not be true any more, I know there have been improvements in this area; check the docs to be sure. But until last year at least, you needed to discriminate between app1's dev stack, and app2's dev stack. So, app1_dev and app2_dev would be appropriate.
little-cartoon-10569
08/08/2023, 12:24 AMTo access outputs of one stack in another stack, you use stack references. The docs and examples are good. https://www.pulumi.com/docs/concepts/stack/#stackreferences
p
prehistoric-translator-89978
08/08/2023, 12:27 AMCoo, cheers.
The
app1_devapp2_devl
little-cartoon-10569
08/08/2023, 12:30 AMLeave the underscore out? 🙂 app1Dev, app2Dev...
little-cartoon-10569
08/08/2023, 12:31 AMIt's just a string. Set up string constants somewhere and ignore the actual strings 🙂
p
prehistoric-translator-89978
08/08/2023, 12:32 AMYes but... If you know you know... Haha... My OCD would forever be unbalanced 🙂
3 Views