Plan does not identify change in Capacity for SpotFleet request.

[udayanms]

Terraform Version

...

Terraform Configuration Files

...vars.tfvars
```SpotFleetTargetCapacity  = "9"



   resource "aws_spot_fleet_request" "SymphonySpotFleet" {
   count = length(var.SpotFleetRequests)
   iam_fleet_role      = "${var.SpotFleetIamFleetRole}"
  #  spot_price          = "0.03"
   allocation_strategy = "diversified"
   target_capacity     = 2
   valid_until         = "2019-11-04T20:44:20Z"
   dynamic "launch_specification" {
     iterator = instanceType
     for_each = var.SpotFleetRequests[count.index].SpotFleetInstanceTypes
     content {
          instance_type            = instanceType.value
          ami                      = "${var.SpotFleetimageId}"
          key_name                 = "${var.SpotFleetKey}"
          spot_price               = "${var.SpotFleetPrice}"
          iam_instance_profile_arn = "${var.SpotFleetIamInstanceProfile}"
          subnet_id                = "${var.SpotFleetSubnetId}"
          weighted_capacity        = "${var.SpotFleetRequests[count.index].SpotFleetWeightedCapacity}"
          tags = var.SpotFleetInstanceTags
    }
   }
  }

Once the SpotFleet was created with SpotFleetTargetCapacity  = "4". I changed the value to 9 but re-running the plan and apply. Nothing changed. 




### Debug Output
<!--
Full debug output can be obtained by running Terraform with the environment variable `TF_LOG=trace`. Please create a GitHub Gist containing the debug output. Please do _not_ paste the debug output in the issue, since debug output is long.
No changes. Infrastructure is up-to-date.

Debug output may contain sensitive information. Please review it before posting publicly, and if you are concerned feel free to encrypt the files using the HashiCorp security public key.
-->

### Crash Output
<!--
If the console output indicates that Terraform crashed, please share a link to a GitHub Gist containing the output of the `crash.log` file.
-->

### Expected Behavior
<!--
What should have happened?
-->

### Actual Behavior
<!--
What actually happened?
-->
No changes. Infrastructure is up-to-date.

### Steps to Reproduce
<!--
Please list the full steps required to reproduce the issue, for example:
1. `terraform init`
2. `terraform apply`
-->

### Additional Context
<!--
Are there anything atypical about your situation that we should know? For example: is Terraform running in a wrapper script or in a CI system? Are you passing any unusual command line options or environment variables to opt-in to non-default behavior?
-->

### References
<!--
Are there any other GitHub issues (open or closed) or Pull Requests that should be linked here? For example:

- #6017

-->

[ghost]

This issue has been automatically migrated to hashicorp/terraform-provider-aws#9322 because it looks like an issue with that provider. If you believe this is not an issue with the provider, please reply to hashicorp/terraform-provider-aws#9322.

[ghost]

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.