Channels
announcements
automation-api
aws
azure
blog-posts
built-with-pulumi
cloudengineering
cloudengineering-support
content-share
contribex
contribute
docs
dotnet
finops
general
getting-started
gitlab
golang
google-cloud
hackathon-03-19-2020
hacktoberfest
install
java
jobs
kubernetes
learn-pulumi-events
linen
localstack
multi-language-hackathon
office-hours
oracle-cloud-infrastructure
package-authoring
pulumi-ai
pulumi-cdk
pulumi-cloud
pulumi-crosscode
pulumi-deployments
pulumi-kubernetes-operator
pulumiverse
python
registry
status
testingtesting123
testingtesting321
typescript
welcome
workshops
yaml
Title
f
fast-river-57630
10/17/2022, 2:30 PMI'm curious about per-region, per-zone deployments in pulumi without multiple stacks.
All my resources can be prefixed with zone and all my actual resource construction is going through a custom factory method so I'm looking at options like 'ignore changes' but that will only get you so far
edit: I guess i want to be able to say "Hey only update, create, and delete objects in this AZ when i do pulumi up".
e
echoing-dinner-19531
10/17/2022, 3:48 PMHave you looked at --targets?
Might give you what you want, although I think we'd generally say if your updating all of one zone at a time that should probably be how your stacks are split up.
f
fast-river-57630
10/17/2022, 4:18 PMyeah I think targets can't do any wildcards?
doing per-zone gets a little combinatorial . N zones * M stacks.
but I could just define 2 'psuedo-zones' that encompass multiple AZs. then i just have prod-1 and prod-2, staging-1 and staging-2 then you get sort of a red/green deployment situation.
oh then i need yet another stack for non-AZ-specific items like VPC. I'll drop this for now.
Thank you
e
echoing-dinner-19531
10/17/2022, 4:42 PMyeah I think targets can't do any wildcards?I think they might, they have issues with wildcards and creating new resources but I think its ok for updates.