Problem creating role since 6.3.0

[chrisyoungbrighte]

Contact Details (optional)

[email protected]

Description. What happened?

Since upgrading to v6.3.0 I am unable to deploy a brand new application. The error I receive is

 | Error: Invalid count argument
 │   on .terraform/modules/ecs-app/iam-ecs-task.tf line 2, in resource "aws_iam_role" "ecs_task":
 │    2:   count = var.task_role_arn != null ? 0 : 1
 │ 

I am providing the ARN of an IAM role. It seems like I would have to deploy that role first in order to avoid this problem?

Steps to reproduce

create a brand new stack with an IAM role and policy and the following configuration:

   new TerraformAwsEcsApp(this, "ecs-app", {
      vpcId: vpc.id,
      albListenerHttpsArn: albListener.arn,
      testTrafficRouteListenerArn: altAlbListener.arn,
      serviceRoleArn: serviceRole.arn,
      taskRoleArn: taskRole.arn,
      name: "service-name",
      image: "hello-world:latest",
      clusterName: cluster.clusterName,
      ecsServiceCapacityProviderStrategy: [],
      autoscalingMin: 1,
      autoscalingMax: 1,
      launchType: "EC2",
      containerPort: 4000,
      hostnameCreate: true,
      hostnames: ["hostname.domain"],
      hostedZone: "domain",
    });

Expected behavior

create the ECS service

Actual behavior

An error forming the plan

Occurrence

Frequently

Relevant log output

│ Error: Invalid count argument
                      │ 
terraform-typescript  │   on .terraform/modules/ecs-app/iam-ecs-task.tf line 2, in resource "aws_iam_role" "ecs_task":
                      │    2:   count = var.task_role_arn != null ? 0 : 1
                      │ 
                      │ The "count" value depends on resource attributes that cannot be determined
                      │ until apply, so Terraform cannot predict how many instances will be created.
                      │ To work around this, use the -target argument to first apply only the
                      │ resources that the count depends on.

Code of Conduct

• I agree to follow this project's Code of Conduct