Channels
pulumi-ai
package-authoring
pulumi-cdk
oracle-cloud-infrastructure
learn-pulumi-events
linen
registry
built-with-pulumi
pulumi-cloud
contribex
testingtesting321
hacktoberfest
cloudengineering
yaml
pulumi-crosscode
content-share
finops
multi-language-hackathon
office-hours
workshops
blog-posts
localstack
welcome
gitlab
pulumi-kubernetes-operator
jobs
aws
pulumi-deployments
dotnet
golang
announcements
java
pulumiverse
python
install
getting-started
cloudengineering-support
testingtesting123
hackathon-03-19-2020
typescript
google-cloud
contribute
azure
kubernetes
docs
automation-api
status
general
Title
l
little-cartoon-10569
01/28/2021, 3:31 AMNot doing it yet, but the thing I want to use it for is for managing accounts with dependencies as stacks with dependencies.
Have you any tips for getting started with setting up VPC peering, Route53 VpcAssociationAuthorization+ZoneAssocation, and similar? Is it enough to have one stack per account? I can see a very-complete pattern that requires 5 stacks (accountAPrePeering, accountBPrePeering, peering, accountADependentOnPeering, accountBDependentOnPeering), but I'd like something a lot simpler...
(AD shared domains would be nice too, but TF doesn't yet support that.)