Plan does not identify change in Capacity for SpotFleet request.

[ghost]

This issue was originally opened by @udayanms as hashicorp/terraform#22050. It was migrated here as a result of the provider split. The original body of the issue is below.

---

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:

- hashicorp/terraform#6017

-->

[AlexanderIakovlev]

Hello @udayanms,

I can't find where you use "SpotFleetTargetCapacity" variable in your code snippet.
In your snippet target_capacity is hard-coded and will be equal "2"

target_capacity = 2

Thanks

[udayanms]

Actually I ran it first with capacity 1 then with 2.

[AlexanderIakovlev]

As i said before looks like you don't use SpotFleetTargetCapacity in this resource.
Please provide more output logs for your plan with option TF_LOG=debug
Thanks

[DrFaust92]

possibly addressed in #12759

[anGie44]

The bug fix has been merged and will release with the upcoming v3.1.0 of the Terraform AWS Provider.

[ghost]

This has been released in version 3.1.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 for triage. Thanks!

[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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!