[Bug]: NULL_IF in file format shows as null in terraform state when set to empty string in Snowflake

[ijeffries]

Terraform CLI Version

5.79.0

Terraform Provider Version

0.99.0

Company Name

National Debt Relief

Terraform Configuration

# snowflake_file_format.create_file_formats["COPY_INTO_FORMAT"] will be updated in-place
  ~ resource "snowflake_file_format" "create_file_formats" {
        id                             = "COPY_INTO_FORMAT"
        name                           = "COPY_INTO_FORMAT"
      ~ null_if                        = [
          ~ null -> "''",
        ]
        # (25 unchanged attributes hidden)
    }

Category

category:resource

Object type(s)

FILE FORMAT

Expected Behavior

I expect the null_if to replace empty strings in my s3 files with NULL. This is how it behaves when I create the file format myself in Snowflake:

alter file format xxx.xxx.COPY_INTO_FORMAT set NULL_IF = ('')

Actual Behavior

I set the nullif to an empty string in terraform (null_if = ["''"]) and it wasn't actually replacing empty strings with NULL when I load from s3. I then ran the above alter command in snowflake and now I get the terraform state mismatch shown in the terraform configuration snippet. Terraform is interpreting alter file format xxx.xxx.COPY_INTO_FORMAT set NULL_IF = ('') as null, and I can't set the terraform configuration to null.

Steps to Reproduce

Create a file format in snowflake with the parameter NULL_IF = ('').

See that you can't get terraform to match, because it interprets this parameter as null from snowflake.

How much impact is this issue causing?

Low

Logs

No response

Additional Information

No response

Would you like to implement a fix?

• Yeah, I'll take it 😎

[sfc-gh-asawicki]

Hey @ijeffries. Thanks for reaching out to us.

The file format resource is still a preview resource in the provider. We will address this problem while reworking it. This issue might be a duplicate of #1609.

For now, treat it as a limitation of the provider.