terraform-provider-aws: Changes in 'launch_specification' of 'aws_spot_fleet_request' are ignored

This issue was originally opened by @DenisBY as hashicorp/terraform#14206. It was migrated here as part of the provider split. The original body of the issue is below.

---

Terraform ignores changing values in launch_specification of aws_spot_fleet_reques

Terraform Version

Terraform v0.9.4

Affected Resource(s)

• aws_spot_fleet_request
• launch_specification

Terraform Configuration Files

variable "volume_type" {
  default = "gp2"
}

resource "aws_spot_fleet_request" "fleet" {
  iam_fleet_role                = "arn:aws:iam::123456789012:role/aws-ec2-spot-fleet-role"
  spot_price                    = "0.114"
  allocation_strategy           = "lowestPrice"
  target_capacity               = 2
  replace_unhealthy_instances   = true
  terminate_instances_with_expiration = true
  valid_until                   = "3000-01-01T00:00:00Z"

  launch_specification {
    ami           = "${var.ecs_ami}"
    instance_type = "${element(var.instance_types[var.ecs_cluster_name], 0)}"
    iam_instance_profile = "ecs-instance-profile"
    key_name      = "${var.ssh_key_name}"
    monitoring  = "false"
    vpc_security_group_ids = ["${split(",", lookup(var.security_groups, var.env_name))}"]
    subnet_id = "${lookup(var.subnet_id_A, var.env_name)}"
    user_data = "${data.template_file.bootstrap.rendered}"
    weighted_capacity = 1

    root_block_device = {
      volume_type = "${var.volume_type}"
      volume_size = "${var.root_volume_size}"
      delete_on_termination = true
    }

    ebs_block_device = {
      device_name = "/dev/xvdcz"
      volume_size = "${var.data_volume_size}"
      volume_type = "${var.volume_type}"
      delete_on_termination = true
    }
  }
}

Expected Behavior

Spot fleet launch_specification is changed

Actual Behavior

Terraform reports: No changes. Infrastructure is up-to-date.

Steps to Reproduce

Please list the steps required to reproduce the issue, for example:

1. terraform apply
2. Change any value in launch_specification, i.e. volume_type or volume_size
3. terraform plan or terraform apply