Alaric Hartmann

> A workaround for this is to compose the Terraform [`jsondecode`](https://www.terraform.io/language/functions/jsondecode) and [`jsonencode`](https://www.terraform.io/language/functions/jsonencode) functions to produce a normalized JSON string: > > ```terraform > resource "awscc_networkmanager_core_network" "main" { > description...

> @tfhartmann A one-off fix for `awscc_networkmanager_core_network.policy_document` was done in #537 which is planned to released in **v0.25.0** of this provider, likely tomorrow. Awesome! Thanks!

We left the default open because we couldn't predict what ports someones tasks might require. For example, a task that launches on an ephemeral port and registers to an alb....

Thanks for opening this issue! Hmm yes, this module is built under the assumption that the EBS volume will be mounted at `/dev/xvdcz` ala this doc... https://docs.aws.amazon.com/AmazonECS/latest/developerguide/ecs-ami-storage-config.html I hadn't considered...

Yes, you can pass in a custom template using the `user_data` parameter. https://github.com/terraform-community-modules/tf_aws_ecs/blob/master/variables.tf#L135

Sorry for the response lag 😄 so here's kind of my thoughts in no particular order. First off thanks you so much for opening #32 thats awesome, I love love...

>What do you think about using locals{} like i did and using a ternary to check if its windows or linux? I really like the idea of using more locals...

It looks like the last PR added a conflict, so this branch may need a rebase.

@joestump awesome thanks! I'll create a new PR to the new repo after we get #23 all closed out!

I'd love to see this fixed and merged, this fixed my issue and let me update `NodeMeta` and start testing with consul-esm