AWS Sqs Queue not setting visibility_timeout_seconds = 0 on create

[ysb33r]

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 v0.12.4

Affected Resource(s)

aws_sqs_queue

Terraform Configuration Files

resource  "aws_sqs_queue" "queue_dead" {
  name                       = "example-sqstest-dead"
  delay_seconds              = 0
  message_retention_seconds  = 1209600
  visibility_timeout_seconds = 0
  receive_wait_time_seconds  = 20
}

Expected Behavior

Queue should be created with visibility timeout of 0s.

Actual Behavior

Queue gets created with default of 30s.

Steps to Reproduce

terraform apply 
terraform show # Visibility timeout is 30s
terraform apply
terraform show # Visibility timeout is 0s

Notes

The issue is probably around this area: https://github.com/terraform-providers/terraform-provider-aws/blob/be67f5e0bfb5a4219a0a371543f037e29e7bd064/aws/resource_aws_sqs_queue.go#L184

It needs a special case for the value being 0, rather than relying on the behaviour of d.getOk.

References

• AWS Sqs Queue not setting visibility_timeout_seconds = 0 on create #750

[github-actions]

This functionality has been released in v3.45.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.