Marcus Hunger

Hi @crazybugliu , any chance you can follow up on this?

The relationship comes through the provider's parameters, doesn't it? e.g. `host = azurerm_kubernetes_cluster.services.kube_config.0.host`

here's the trace. I've cut away the state dumps containing secrets. Hope it's still helpful. I've also attached the graph as an svg. https://gist.github.com/fnordian/903c683f7fbe86071fcb4995b680e7eb 

sorry, fixed. (it was a b)

Using `data` in between resource and provider works around that problem. Although now I am running into what seems to be https://github.com/hashicorp/terraform-provider-kubernetes/issues/1028 ```terraform data "azurerm_kubernetes_cluster" "services" { name = var.cluster_name...

Please note that they failure doesn't show on the initial apply, but only on the update. As provider declarations allow references to other resources, it's hard to understand where the...

Hello @dieppa ,  The document is: ``` { "_id" : ObjectId("5f291e43cdbd9b0eec9fb1a9"), "executionId" : "2018-10-14T08:14:53.446535-839", "changeId" : "init", "author" : "", "timestamp" : { "$date" : "2018-10-14T08:14:53.302Z" }, "state" :...

The initial MongoDB was 4.0. That's when the first entries have been inserted. Spring Boot 2.0.3.RELEASE was used. So it should have been mongodb-driver 3.6.4. That's the oldest driver that...

Has this been resolved? I've got the same problem on fedora 16 64bit. idea.log doesn't show anything suspicious.