Terraform plan does not detect updates when graphs updated outside terraform about terraform-provider-datadog

The schema.ResourceData isn't getting populated. Things are failing but errors are being silently ignored. In the resourceDatadogTimeboardRead function, the call to schema.ResourceData.Set fails but isn't caught. If I make the change to check errors, the failures are there and the errors vary with each run:

k@Thor ~/test> terraform import datadog_timeboard.my_timeboard 361820
datadog_timeboard.my_timeboard: Importing from ID "361820"...
Error importing: 1 error(s) occurred:

* datadog_timeboard.my_timeboard (import id: 361820): import datadog_timeboard.my_timeboard (id: 361820): Invalid address to set: []string{"graph", "0", "group"}
k@Thor ~/test [1]> terraform import datadog_timeboard.my_timeboard 361820
datadog_timeboard.my_timeboard: Importing from ID "361820"...
Error importing: 1 error(s) occurred:

* datadog_timeboard.my_timeboard (import id: 361820): import datadog_timeboard.my_timeboard (id: 361820): Invalid address to set: []string{"graph", "0", "events"}
k@Thor ~/test [1]> terraform import datadog_timeboard.my_timeboard 361820
datadog_timeboard.my_timeboard: Importing from ID "361820"...
Error importing: 1 error(s) occurred:

* datadog_timeboard.my_timeboard (import id: 361820): import datadog_timeboard.my_timeboard (id: 361820): graph.0.include_ungrouped_hosts: '' expected type 'bool', got unconvertible type '*bool'

My guess is that it has to do with the refactor of the client library to generate its accessor methods and move to pointers for all the fields coupled with Terraform's use of the reflect library to anticipate a need for dereference.

The solution isn't immediately obvious to me but I can take another look at it in a while.

[nyanshak]

I believe this was fixed in #27. Can close this once it gets added to a release.