https://pulumi.com logo
i

important-leather-28796

12/18/2019, 4:53 PM
I’m experimenting with restricted cluster sizes for development and I’d like to reduce my cycle time by reducing the default wait for error on
pulumi update
, how do I do that? I already pulled down the Deployment wait time with
<http://pulumi.com/timeoutSeconds|pulumi.com/timeoutSeconds>
but the continued retries/restarts (resource limits are being hit) do not cause
pulumi
to exit for quite a while. How can I reduce retries/shorten this wait or cycle time as I experiment?
I added a temporary
restartPolicy: 'Never'
but would prefer to not modify this config - don’t want to accidentally leave it in.
Yikes, I guess that doesn’t work
Deployment.apps “api” is invalid: spec.template.spec.restartPolicy: Unsupported value: “Never”: supported values: “Always”
So, I’m still stuck waiting for
pulumi update
to return
g

gorgeous-egg-16927

12/18/2019, 8:10 PM
You should be able to manage timeouts for any Pulumi resource using the
customTimeouts
resource opt: https://www.pulumi.com/docs/reference/pkg/nodejs/pulumi/pulumi/#CustomResourceOptions-customTimeouts
👍 1
If that doesn’t do the trick for you, please open an issue and we’ll take a look