pulumi-aws icon indicating copy to clipboard operation
pulumi-aws copied to clipboard

Creating an ACM Certificate always times out and custom timeouts not respected

Open VenelinMartinov opened this issue 1 year ago • 1 comments

What happened?

The default timeout on ACM Certificate of 5m seems to be insufficient in most cases. This causes the creation to timeout before it manages to create the resource.

Example

name: acm
runtime: yaml
resources:
  certificate:
    type: aws:acm:Certificate
    properties:
      domainName: "example.com"
      validationMethod: "EMAIL"
      subjectAlternativeNames: ["www.example.com"]

Moreover the customTimeout option is not respected:

    options:
      customTimeouts:
        create: "30m"

This still fails after 5m

Output of pulumi about

CLI          
Version      3.108.1
Go Version   go1.22.0
Go Compiler  gc

Plugins
NAME  VERSION
aws   unknown
yaml  unknown

Host     
OS       darwin
Version  14.1.1
Arch     arm64

This project is written in yaml

Current Stack: pulumi/acm/dev

Found no resources associated with dev

Found no pending operations associated with dev

Backend        
Name           pulumi.com
URL            https://app.pulumi.com/venelin-pulumi-corp
User           venelin-pulumi-corp
Organizations  venelin-pulumi-corp, demo, pulumi
Token type     personal

No dependencies found

Pulumi locates its logs in /var/folders/82/nqnqw81s1h56l5nv940f9mq00000gn/T/ by default

AWS 6.25, also tested in 6.25.1

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction. To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

VenelinMartinov avatar Mar 13 '24 11:03 VenelinMartinov

https://github.com/hashicorp/terraform-provider-aws/blob/master/internal/service/acm/certificate.go#L331 it looks like *schema.ResourceData is not used as a source of the timeout information in the upstream code for resourceCertificateCreate, instead it decides on constant timeouts. So this looks like an upstream issue not a bridge one, which we could address by patching.

t0yv0 avatar Mar 14 '24 17:03 t0yv0

Possibly related https://github.com/hashicorp/terraform-provider-aws/issues/13031 though on an adjacent validation resource not this one.

t0yv0 avatar Mar 29 '24 20:03 t0yv0