awscc_deadline_limit : perpetual drift on subsequent runs

[quixoticmonk]

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
• The resources and data sources in this provider are generated from the CloudFormation schema, so they can only support the actions that the underlying schema supports. For this reason submitted bugs should be limited to defects in the generation and runtime code of the provider. Customizing behavior of the resource, or noting a gap in behavior are not valid bugs and should be submitted as enhancements to AWS via the CloudFormation Open Coverage Roadmap.

Terraform CLI and Terraform AWS Cloud Control Provider Version

Terraform v1.10.0
on darwin_amd64
+ provider registry.terraform.io/hashicorp/awscc v1.28.0

Affected Resource(s)

• awscc_deadline_limit

Terraform Configuration Files

# Create the Deadline Farm
resource "awscc_deadline_farm" "example" {
  display_name = "ExampleFarm"
  description  = "Example Deadline Farm created with AWSCC provider"

  tags = [{
    key   = "Modified By"
    value = "AWSCC"
  }]
}

# Create a Deadline limit
resource "awscc_deadline_limit" "example" {
  farm_id = awscc_deadline_farm.example.farm_id
  display_name    = "example"
  max_count   = 100  
  amount_requirement_name="amount.example"
}

Debug Output

Panic Output

Expected Behavior

• Deadline limit should be provisioned without issues.

Actual Behavior

terraform apply shows perpetual drift on the awscc_deadline_limit resource on a property which is not a user input.

awscc_deadline_farm.example: Refreshing state... [id=arn:aws:deadline:us-east-1:############:farm/farm-3f209dc4df6d4e4a8944e0cfe5386e08]
awscc_deadline_limit.example: Refreshing state... [id=farm-3f209dc4df6d4e4a8944e0cfe5386e08|limit-1b23dd741d444eccb8d8b9d48e6c35b5]

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
  ~ update in-place
Terraform will perform the following actions:
  # awscc_deadline_limit.example will be updated in-place
  ~ resource "awscc_deadline_limit" "example" {
        id                      = "farm-3f209dc4df6d4e4a8944e0cfe5386e08|limit-1b23dd741d444eccb8d8b9d48e6c35b5"
        # (7 unchanged attributes hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.
awscc_deadline_limit.example: Modifying... [id=farm-3f209dc4df6d4e4a8944e0cfe5386e08|limit-1b23dd741d444eccb8d8b9d48e6c35b5]
awscc_deadline_limit.example: Modifications complete after 5s [id=farm-3f209dc4df6d4e4a8944e0cfe5386e08|limit-1b23dd741d444eccb8d8b9d48e6c35b5]

Apply complete! Resources: 0 added, 1 changed, 0 destroyed.

Steps to Reproduce

1. terraform apply
2. terraform apply

Important Factoids

References