aws_s3_bucket timeouts block support (deletion)

[azhurbilo]

Description

Terraform can not delete s3 bucket if it contains files (force_destroy Default:false) and it's absolutely ok.

But "apply" phase retry deletion infinitely

module.alb.aws_s3_bucket.xxx[0]: Still destroying... [id=xxx, 1h58m41s elapsed]
module.alb.aws_s3_bucket.xxx[0]: Still destroying... [id=xxx, 1h58m51s elapsed]
module.alb.aws_s3_bucket.xxx[0]: Still destroying... [id=xxx, 1h59m1s elapsed]
module.alb.aws_s3_bucket.xxx[0]: Still destroying... [id=xxx, 1h59m11s elapsed]
...

in our case Bitbucket CI has 2 hour max build time, after that time Terraform forcely stopped - part of applied stated was lost :(

resource "aws_s3_bucket" "s3_bucket" {
  ...
  timeouts {
    create = "60m"
    delete = "60m"
    update = "60m"
  }
}

Error: Unsupported block type
 in resource "aws_s3_bucket" "s3_bucket":
  92:   timeouts {
Blocks of type "timeouts" are not expected here.

not supported by "aws_s3_bucket"

New or Affected Resource(s)

• aws_s3_bucket

References

• https://www.terraform.io/docs/configuration/resources.html#operation-timeouts

[github-actions]

This functionality has been released in v4.25.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading.

For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you!

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.