https://pulumi.com logo
Title
h

hallowed-rain-9096

03/17/2021, 9:11 PM
I'm having some trouble with
pulumi up
going for more than 10 minutes without output, which causes CircleCI (my CI provider) to kill the job. Is there a better option than just turning up the verbosity until it no longer happens?
This is happening because I'm waiting on slow-to-create resources, btw 😉 thanks!
b

bored-oyster-3147

03/17/2021, 11:54 PM
My first thought would be to see if I could do anything about that timeout time limit, but I haven’t used Circle CI
That said I think short of increasing verbosity I’m not sure there is a way to get circumvent that timeout without automation api
You could write an app with automation API that gives you regular log message if the update is still running to get around that, but you would lose some of the pretty well formatted logs of using the CLI, though that may not matter inside a pipeline
h

hallowed-rain-9096

03/18/2021, 2:09 PM
what I'd love is a configurable interval to display a "waiting" message a la
pulumi up --yes --wait-message-interval=300
b

bored-oyster-3147

03/18/2021, 2:31 PM
that would be nice and I suspect you wouldn't be the only one to find it useful in pipelines that will timeout like that. Maybe open an issue?
slow deploying resources can be a bit of a pain for sure
h

hallowed-rain-9096

03/18/2021, 2:52 PM
Issue created - please upvote if you find this useful https://github.com/pulumi/pulumi/issues/6574
👀 1