David Rubin

Have you tried to include ``` driver_opts: WEAVE_MULTICAST: 1 ``` https://docs.docker.com/compose/compose-file/#network-configuration-reference It might work to explicitly set the driver opts params on the stack.

Thanks derek this fixes it for me as well.. Maybe the owner of the project could actually accept this patch? Have you submitted a pull request?

But it does support it easily with the premium version. https://uptimerobot.com/api#newMonitorWrap While we are abstracting away these thigns it might also be nice to abstract away the AlertContacts as well....

Nope this isn't fully addressed but we can rename it to something that clearly states it doesn't support Terraform 0.12.?

@dlespiau sounds perfect. I hadn't gotten around to it yet but I am very eggerly waiting to try move some of our Terraform code to this. But we use 0.12...

https://github.com/hashicorp/hcl/wiki/Version-Selection I think if we switch to v2 of the hcl library we might get even closer

I get the same errors on GKE ```kube-state-metrics-cbb74cc9c-qmkfz kube-state-metrics E0625 08:38:56.316733 1 reflector.go:205] k8s.io/kube-state-metrics/collectors/cronjob.go:93: Failed to list *v2alpha1.CronJob: the server could not find the requested resource kube-state-metrics-cbb74cc9c-qmkfz kube-state-metrics E0625 08:38:57.318844...

/remove-lifecycle rotten

I think we should release a 0.10 with fluent Api and 1.15 bindings before going to 1 0 I can foresee a few issues poping up from adding fluent bindings...

I also think #53 might be a relevant fix before 1.0