Channels
welcome
pulumi-cdk
cloudengineering
yaml
blog-posts
localstack
pulumi-ai
package-authoring
general
pulumiup-booth-support
oracle-cloud-infrastructure
learn-pulumi-events
linen
registry
built-with-pulumi
pulumi-cloud
contribex
testingtesting321
hacktoberfest
pulumi-crosscode
content-share
finops
multi-language-hackathon
office-hours
workshops
gitlab
pulumi-kubernetes-operator
jobs
pulumi-deployments
dotnet
aws
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
Powered by
#general
Title
a
acceptable-army-69872
11/26/2019, 7:44 PM
Takes a good long time for cloudfront distro's to finish updating, but pulumi up wants to wait for it. Is that the expected behavior?
b
broad-dog-22463
11/26/2019, 7:45 PM
Yes because if it fails then Pulumi won’t know it failed on the next run
a
acceptable-army-69872
11/26/2019, 7:47 PM
Makes sense. Distro updates can be like 20 minutes which is the hairy edge of timeouts right?
g
gentle-diamond-70147
11/26/2019, 8:04 PM
You can set custom timeouts if you like.
https://www.pulumi.com/docs/intro/concepts/programming-model/#customtimeouts
Post