Redshift cluster when paused returns single-node cluster-type when it is multi-node

[neillturner]

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_version: 0.14.7

• Installing hashicorp/aws v3.59.0...

Affected Resource(s)

aws_redshift_cluster

Terraform Configuration Files

resource "aws_redshift_cluster" "this" {
  cluster_identifier = "tf-redshift-cluster"
  database_name      = "mydb"
  master_username    = "foo"
  master_password    = "Mustbe8characters"
  node_type          = "dc1.large"
  cluster_type       = "multi-node"
}

Debug Output

running terraform plan shows

module.dev_mi_alpha_ra3.aws_redshift_cluster.this will be updated in-place ~ resource "aws_redshift_cluster" "this" { ~ cluster_type = "single-node" -> "multi-node"

Expected Behavior

running terraform plan should show no change

Actual Behavior

tries to change cluster_type "single-node" -> "multi-node"

Steps to Reproduce

create a multi-node redshift cluster pause redshift cluster in aws console rerun terraform again. plan will show it will try to change "single-node" -> "multi-node" apply will fail trying to change "single-node" -> "multi-node"

1. terraform apply

Important Factoids

No

References

https://github.com/hashicorp/terraform-provider-aws/issues/12745 Add support for Redshift scheduled actions #12745

when this is added then it will be possible to have scheduled actions that pause and resume redshift which will mean terraform wont run when cluster is paused when folks try to update something else.

Also adding this so others can find this issue when they search the internet.

• 0000

[nwsparks]

this could use a bump.

[xsnrg]

still happening with terraform 1.6.5 and AWS provider 5.30.0