Update docs on aws_cloudwatch_event_target's ecs_target.task_count tosay it is required

[alex]

The docs previously said it defaulted to 1 and was optional, but actually omitting the value produced an AWS error:

Error: Creating CloudWatch Event Target failed: InvalidParameter: 1 validation error(s) found.

• minimum field value of 1, PutTargetsInput.Targets[0].EcsParameters.TaskCount.

Community Note

• Please vote on this pull request by adding a 👍 reaction to the original pull request comment to help the community and maintainers prioritize this request
• Please do not leave "+1" comments, they generate extra noise for pull request followers and do not help prioritize the request

Release note for CHANGELOG:

NONE

Output from acceptance testing:

$ make testacc TESTARGS='-run=TestAccXXX'

...

[aeschright]

Thanks @alex -- could I have a look at the relevant section of your config? From the code it looks like the documentation should be correct, so I'd like to figure out where that error is coming from.

[alex]

resource "aws_cloudwatch_event_rule" "scheduled_task" {
  name                = var.name
  description         = "Run ${var.name} on schedule: ${var.schedule_expression}"
  schedule_expression = var.schedule_expression
}

resource "aws_cloudwatch_event_target" "task_target" {
  rule     = aws_cloudwatch_event_rule.scheduled_task.name
  arn      = var.cluster_arn
  role_arn = aws_iam_role.event_role.arn

  ecs_target {
    launch_type         = "FARGATE"
    platform_version    = "LATEST"
    task_definition_arn = var.task_definition_arn
    task_count          = 1
    network_configuration {
      subnets         = var.subnet_ids
      security_groups = var.security_group_ids
    }
  }
}

is the relevant bit, without the task_count = 1 line I get the error I indicated.

[aeschright]

The underlying bug was fixed in #9773 and released with v2.25.0. Thanks for pointing us to this problem!

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