[Enhancement]: Add configurable timeouts for aws_organizations_account

[erpel]

Description

When deleting an aws_organizations_account it can take more than the default 5 minutes. Sometimes it does not.
I'm experiencing this with the close_on_deletion = true setting.

Being able to define a slightly longer timeout might allow completing terraform runs to remove accounts without having to retry. Usually on a retry a few minutes later, all is good.

* Failed to execute "terraform apply -auto-approve -input=false" in .
  ╷
  │ Error: waiting for AWS Organizations Account (123…) delete: timeout while waiting for resource to be gone (last state: 'ACTIVE', timeout: 5m0s)
  │ 
  │ 
  ╵

Affected Resource(s) and/or Data Source(s)

• aws_organizations_account

Potential Terraform Configuration

resource "aws_organizations_account" "sometest" {

  name      = "sometest"
  email     = "aws-accounts+sometest@….com"
  role_name = "account-bootstrap-role"
  parent_id = "foo"
  close_on_deletion = true
  
  timeouts {
    delete = "20m"
  }

}

References

No response

Would you like to implement a fix?

None

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[github-actions]

Warning

This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.

Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.