Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

GoodData writer 'Read' fails when the writer is set to do Full load #28

Open
plmwong opened this issue Aug 3, 2017 · 1 comment
Open

GoodData writer 'Read' fails when the writer is set to do Full load #28

plmwong opened this issue Aug 3, 2017 · 1 comment
Labels
bug

Comments

@plmwong
Copy link
Contributor

plmwong commented Aug 3, 2017

When a GoodData writer has been configured to do a Full load to GoodData instead of an Incremental, then a terraform plan or terraform refresh will fail with an error about unmarshaling a boolean in to an integer. So there will be a type mismatch between what is in the JSON response when the GoodData writer is set to Full.
@plmwong plmwong added the bug label Aug 3, 2017
@plmwong
Copy link
Contributor Author

plmwong commented Aug 3, 2017

Looks like when a Full load is configured, then:

"incrementalLoad":false

But when an Incremental load is configured, then:

"incrementalLoad":2

So the same property in JSON can have either boolean or integer values. Will need to follow up with Keboola about this, or implement a hybrid Go type.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@plmwong