-
Notifications
You must be signed in to change notification settings - Fork 89
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.
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
Check type casts to void crashing when casting explicit null values #534
Conversation
017de81
to
df013c8
Compare
@tobio can you please check why acceptance tests failed |
This test appears to be failing due to hashicorp/terraform-plugin-sdk#1066 and hashicorp/terraform-plugin-sdk#1073 (seem to be duplicates). I've updated the acceptance tests to run against 1.2.9 in CI until the TF issue is fixed. |
cc2811f
to
4f9cec1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code LGTM
4f9cec1
to
f76d470
Compare
…lastic#534) * Ignore fields explicitly set to null in Kibana resources * Ignore fields explicitly set to null in APM resources * Ignore fields explicitly set to null in ES resources * Ignore fields explicitly set to null in Enterprise Search resources * Ignore fields explicitly set to null in Integrations Server resources * Ignore fields explicitly set to null in observability resources * Ignore fields explicitly set to null in azure private endpoint resources * Changelog
Description
Repro in the linked issue.
Some fields may be sourced from Terraform variables, if those variables are optional then it's not uncommon to explicitly set fields to null, which the provider should treat as if the field was left unset.
Related Issues
Fixes #522
How Has This Been Tested?
Unit tests
Manually
Types of Changes
Readiness Checklist