Closed aairey closed 2 years ago
@aairey How are you producing this?
I've supplied null
to container_cpu
in fixtures.us-east-2.tfvars
in examples/complete
and can produce a clean plan:
region = "us-east-2"
namespace = "eg"
stage = "test"
name = "container-definition"
container_name = "app"
container_image = "cloudposse/geodesic"
container_memory = 256
container_memory_reservation = 128
#container_cpu = 256
container_cpu = null
essential = true
readonly_root_filesystem = false
container_environment = [
{
name = "string_var"
value = "I am a string"
},
{
name = "true_boolean_var"
value = true
},
{
name = "false_boolean_var"
value = false
},
{
name = "integer_var"
value = 42
}
]
port_mappings = [
{
containerPort = 8080
hostPort = 80
protocol = "tcp"
},
{
containerPort = 8081
hostPort = 443
protocol = "udp"
}
]
log_configuration = {
logDriver = "json-file"
options = {
"max-size" = "10m"
"max-file" = "3"
}
secretOptions = null
}
privileged = false
extra_hosts = [{
ipAddress = "127.0.0.1"
hostname = "app.local"
},
]
hostname = "hostname"
pseudo_terminal = true
interactive = true
That additional information that's useful for bug reports such as these is included in our issue template... looks like you didn't use it.
The variable defaults to 0, but it is allowed to leave it unset.
https://registry.terraform.io/providers/hashicorp/aws/latest/docs/resources/ecs_task_definition#cpu https://docs.aws.amazon.com/AmazonECS/latest/developerguide/task_definition_parameters.html
IMHO, we should allow to pass
null
to this module.