Hey, we're testing the Consul ECS v0.8.0 terraform module, more specifically the mesh-task.
While testing we've found that after applying the changes, subsequent plans will keep displaying perpetual diffs in the container definitions about default values not being present. This doesn't happens in the v0.7.1 at least.
Terraform version: v1.3.7
AWS Provider version: v5.50.0
ECS deployment model: Fargate (meaning variable enable_transparent_proxy is set to false, this is relevant as per my findings).
Hey, we're testing the Consul ECS v0.8.0 terraform module, more specifically the mesh-task.
While testing we've found that after applying the changes, subsequent plans will keep displaying perpetual diffs in the container definitions about default values not being present. This doesn't happens in the v0.7.1 at least.
Terraform version: v1.3.7 AWS Provider version: v5.50.0 ECS deployment model: Fargate (meaning variable
enable_transparent_proxy
is set to false, this is relevant as per my findings).Perpetual drift:
From my investigation, basically the issue seems related to the empty dictionary
capabilities
insidelinuxParameters
.The initial apply creates this an empty
capabilities
dict insidelinuxParameters
dict:The subsequent plan tries to change it to null:
To avoid this, I need to slighty adjust the
linuxParameters
: https://github.com/hashicorp/terraform-aws-consul-ecs/pull/319