aws_connect_contact_flow should destroy/create when type changes

[smastrorocco]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• 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
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform CLI and Terraform AWS Provider Version

Terraform v1.2.9
on darwin_amd64
+ provider registry.terraform.io/hashicorp/aws v4.30.0

Affected Resource(s)

• aws_connect_contact_flow

Terraform Configuration Files

resource "aws_connect_instance" "this" { ... }

resource "aws_connect_contact_flow" "this" {
  instance_id = aws_connect_instance.this.id
  ...
  type = "CONTACT_FLOW" # Create and update to new value, like QUEUE_TRANSFER
}

Expected Behavior

The current Amazon Connect API does not currently support updating the type for Contact Flow. The expected behavior from Terraform would be a forced recreate action (destroy/create).

Actual Behavior

Terraform plan shows the type changing, and upon apply updates the state file, but is a no-op in Connect, and the Contact Flow remains the original type.

Terraform will perform the following actions:
  ...
  ~ resource "aws_connect_contact_flow" "this" {
        ...
      ~ type            = "CONTACT_FLOW" -> "QUEUE_TRANSFER"
        # (5 unchanged attributes hidden)
    }
Plan: 0 to add, 1 to change, 0 to destroy.

Steps to Reproduce

Create an aws_connect_contact_flow of any type and apply it, then update the type to a new value, and plan/apply it.

1. terraform apply

[github-actions]

This functionality has been released in v4.37.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.