GetOkExists returns false during create when empty value is specified for List type

[parweza]

HI,
GetOkExists returns false during create when empty value is specified for List type. Because of that We are not able differentiate whether customer has omitted this field in tf config or has provided empty value.

resource "oci_file_storage_export" "my_export_fs1_mt1" {
  #Required
  export_set_id  = "${oci_file_storage_export_set.my_export_set_1.id}"
  file_system_id = "${oci_file_storage_file_system.my_fs_1.id}"
  path           = "${var.export_path_fs1_mt1}"

  export_options = [
  ]
}

with above config we are expecting to get true for ok onhttps://github.com/oracle/terraform-provider-oci/blob/master/provider/file_storage_export_resource.go#L177
but we are getting false.
Can you please look into it?

Thanks,
Parwez

Terraform Version

0.10.8

Terraform Configuration Files

...

Debug Output

Crash Output

Expected Behavior

Actual Behavior

Steps to Reproduce

Additional Context

References

[jbardin]

Hi @parweza,

Sorry about the confusion here, but this is working as expected. From the GetOkExists docs, you can see:

This is only useful for determining if boolean attributes have been set, if they are Optional but do not have a Default value

There is no notion of "unset" in the current schema packages. We are working on new protocol and configuration packages that will support this in the future, but for now the zero values can't be differentiated from unset in the in config.

[parweza]

@jbardin
what is recommended way differentiating the cases when user has omitted the property and when provided empty value?
we need to model
export options in https://docs.cloud.oracle.com/iaas/api/#/en/filestorage/20171215/datatypes/CreateExportDetails

[jbardin]

@parweza,

Unfortunately there is not currently a method for determining this in all cases. We are in the process of updating the configuration language to support this feature, but it's going to be some time before it's fully supported in the provider sdk.

In the meantime, this usually requires the use of a sentinel value for the empty set, or another option field to indicate that the user wants to set no export options.

[mingfang]

any update on this?

[paultyng]

This will most likely be solved by #261 given explicit access to Unknown vs empty list and #133 which will provide direct access to config values. Closing in favor of those.

[ghost]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.