Consul Client Command Incompatible with Fargate

hashicorp / terraform-aws-consul-ecs

Consul Service Mesh on AWS ECS (Elastic Container Service)

https://www.consul.io/docs/ecs

Mozilla Public License 2.0

52 stars 30 forks source link

Consul Client Command Incompatible with Fargate #23

Closed reskin89 closed 3 years ago

reskin89 commented 3 years ago

Currently:

https://github.com/hashicorp/terraform-aws-consul-ecs/blob/c21817663d280f77e2aa51d5cc0251ea95744525/modules/mesh-task/templates/consul_client_command.tpl#L1

The Consul Client Command template does a curl against ECS_CONTAINER_METADATA_URI, Fargate now uses ECS_CONTAINER_METADATA_URI_V4 which the consul-ecs binary in the ecs container looks for, but the client command does not.

This makes the module incompatible with fargate.

pglass commented 3 years ago

Hi @reskin89!

We actually have acceptance tests which run on Fargate, so we know this works (or has worked, at least, when they last ran).

Are you seeing an error using ECS_CONTAINER_METADATA_URI in Fargate?