[Bug]: aws_appautoscaling_target failed to create with - "ValidationException: Tag values cannot be empty or blank"

[shira-lev]

Terraform Core Version

1.4.6

AWS Provider Version

4.66.1

Affected Resource(s)

aws_appautosacling_target

Expected Behavior

Resource should have been created with no errors

Actual Behavior

When attempting to create the resource with an equal configuration to the one presented in the docs I'm receiving this error -
creating Application AutoScaling Target (table/XXX): ValidationException: Tag values cannot be empty or blank

Relevant Error/Panic Output Snippet

No response

Terraform Configuration Files

I am using this module to create an autoscaling target to my DynamoDB - cloudposse/dynamodb-autoscaler/aws
The aws_autoscaling_target configuration is -

resource "aws_appautoscaling_target" "read_target" {
  count              = module.this.enabled ? 1 : 0
  max_capacity       = var.autoscale_max_read_capacity
  min_capacity       = var.autoscale_min_read_capacity
  resource_id        = "table/${var.dynamodb_table_name}"
  scalable_dimension = "dynamodb:table:ReadCapacityUnits"
  service_namespace  = "dynamodb"
}

The values to these parameters are -
dynamodb_table_name: XXX
autoscaleMinReadCapacity: 30
autoscaleMaxReadCapacity: 60

Steps to Reproduce

run Terraform plan successfully and failed with Terraform apply

Debug Output

No response

Panic Output

No response

Important Factoids

I am running terraform with cdktf version 0.15.5

References

No response

Would you like to implement a fix?

None

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• 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.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[justinretzolk]

Hey @shira-lev 👋 Thank you for taking the time to raise this! So that we have the necessary information in order to look into this, can you supply debug logs (redacted as needed) as well?

[shira-lev]

Hi, so we found what caused the problem, we were using default tags at provider level and one of the tags was an empty string by mistake, after we changed its value we were able to run the deploy.

[justinretzolk]

Thank you for following up on this one! With that information in mind, we'll close this one out.

[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.