No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Pulumi Community

should customTimeouts propagate from parent resource down? seems that it doesn't, at least not for the helm chart

Currently, it only applies to the individual resources, not component resources like Charts. You can file an issue if you’ve got a use case in mind

well, all I want that individual resources to inherit timeouts from parent (== chart) same way as they inherit provider

Different resource types have different default timeouts

So not quite the same as the provider, but we’re happy to consider the case with some more info about what you were expecting

trying this so far:

```
transformations: [
            // we cant set timeout on a chart level yet, so set it for all resources
            /* eslint-disable-next-line @typescript-eslint/no-explicit-any */
            (_o: any, opts: CustomResourceOptions) =&gt; {
                opts.customTimeouts = { create: "60s", update: "60s" };
            },
```