Inconsistent results after apply, when es or kibana config yaml is set to "".

Readiness Checklist

• I am running the latest version
• I checked the documentation and found no answer
• I checked to make sure that this issue has not already been filed
• I am reporting the issue to the correct repository (for multi-repository projects)

Expected Behavior

Values will be consistent after apply

Current Behavior

│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to module.main.module.ec_deployment_setup.ec_deployment.elastic, provider
│ "provider["registry.terraform.io/elastic/ec"]" produced an unexpected new value:
│ .elasticsearch.config.user_settings_yaml: was cty.StringVal(""), but now null.
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.
╵
╷
│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to module.main.module.ec_deployment_setup.ec_deployment.elastic, provider
│ "provider["registry.terraform.io/elastic/ec"]" produced an unexpected new value:
│ .kibana.config: was cty.ObjectVal(map[string]cty.Value{"docker_image":cty.NullVal(cty.String),
│ "user_settings_json":cty.NullVal(cty.String),
│ "user_settings_override_json":cty.NullVal(cty.String),
│ "user_settings_override_yaml":cty.NullVal(cty.String), "user_settings_yaml":cty.StringVal("")}),
│ but now null.
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.
## Terraform definition

Steps to Reproduce

Context

Possible Solution

Your Environment

• Version used:
• Running against Elastic Cloud SaaS or Elastic Cloud Enterprise and version:
• Environment name and version (e.g. Go 1.9):
• Server type and version:
• Operating System and version:
• Link to your project: