Tracking: timeout-related issues

[t0yv0]

Opening a tracking list to not lose this in G-docs, although it is not entirely clear all these issues originate in the bridge. They do skew to bridged-providers though.

• p/p Custom Timeouts ignored for ASG in Python (maybe other resources and/or languages) #12987
• https://github.com/pulumi/pulumi-terraform-bridge/issues/1651

awsx

• autoscaling - custom timeouts are not propagated to child resources #530

• Fargate service updating failing with timeout #354 (The actual failure is a different issue but custom timeouts had no effect)

aws

• customTimeouts not honored for ecs.Service #1336 (Closed but I’m not sure that’s correct)
• aws NodeGroup set with customTimeout on update to 4h hits a timeout error of 20m #3442

eks

eks Custom timeouts are not propagated to child resources #393

[t0yv0]

@thomas11 thanks for the original list