Hello all. Can anybody tell me why a ResourceOptions custom timeout on a dynamic provider would be being ignored? Is it expected that the provider will implement that functionality?

Yes - it is up to the provider, and I believe Dynamic Providers may not (yet) have the ability to opt-in to using it. This is something that should be possible to expose to the Dynamic Provider API.

Is there any documentation I can read on how (if at all) ResourceOptions passed from the resource to the provider/how to read the options from the provider? Or is that something I should be implementing as well?

The underlying provider interface is defined in https://github.com/pulumi/pulumi/blob/master/sdk/proto/provider.proto. All resource providers ultimately implement that interface - but we provide several approaches to implementing it (in Go using higher level libraries, bridged from a Terraform Provider, or using Dynamic Providers in Python and Node.js which implement the interface in terms of calls to dynamic provider functions). You can see there that the only "resource option" that gets passed through to providers is

timeout

- for example on

CreateRequest

. The problem is just that we have not yet plumbed that through into dynamic providers. It wouldn't be hard to do that - but it isn't exposed yet. If you'd like to open an issue in GitHub, someone can look at it (or PRs very welcome!)

Thank you, I will definitely look at opening a PR.