The cloud-connector-ecs service module has a Terraform resource that defines an aws_ecs_service, but that resource is missing the optional argument of propagate_tags.

Unless this argument is defined, the running ECS Tasks will not have Tags, even if any default_tags have been specified in the aws provider configuration code. This poses an issue when attempting to properly track AWS costs by resource tagging.

Would it be possible to add the propagate_tags argument to this aws_ecs_service and set it to either SERVICE or TASK_DEFINITION?