[Bug]: Table Column Updates are not recognized by Terraform Provider

JESCHO99 commented 2 months ago

Terraform CLI Version

1.5.7

Terraform Provider Version

0.94.1

Terraform Configuration

terraform {
  required_version = "~> 1.5.0"
  required_providers {
    snowflake = {
      source  = "Snowflake-Labs/snowflake"
      version = "~> 0.94.0"
    }
  }
}

provider "snowflake" {
  role = "SYSADMIN"
}

resource "snowflake_database" "this" {
  name = "TEST_DATABASE"
}

resource "snowflake_schema" "this" {
  database                    = snowflake_database.this.name
  name                        = "TEST_SCHEMA"
  is_transient                = "false"
  with_managed_access         = "false"
  data_retention_time_in_days = 1
}

resource "snowflake_table" "table_1" {
  database                    = snowflake_database.this.name
  schema                      = snowflake_schema.this.name
  name                        = "TEST_TABLE_V1"
  data_retention_time_in_days = 1
  change_tracking             = false

  column {
    name = "ID"
    type = "NUMBER"
  }

  column {
    name = "NAME"
    type = "VARCHAR(3)"
  }
}

resource "snowflake_table" "table_2" {
  database                    = snowflake_database.this.name
  schema                      = snowflake_schema.this.name
  name                        = "TEST_TABLE_V2"
  data_retention_time_in_days = 1
  change_tracking             = false

  column {
    name = "ID"
    type = "NUMBER(11,2)"
  }

  column {
    name = "NAME"
    type = "VARCHAR(255)"
  }
}

Object type(s)

resource:table

Expected Behavior

The code provided above could be applied to a Snowflake Account without any problem. If you change the data type of a column for example change the "type" of the column "NAME" in the snowflake table "TEST_TABLE_V2" to "VARCHAR(3)" the next terraform plan should recognize this change and provide a plan how this change could be applied to the backend.

resource "snowflake_table" "table_2" {
  database                    = snowflake_database.this.name
  schema                      = snowflake_schema.this.name
  name                        = "TEST_TABLE_V2"
  data_retention_time_in_days = 1
  change_tracking             = false

  column {
    name = "ID"
    type = "NUMBER(11,2)"
  }

  column {
    name = "NAME"
    type = "VARCHAR(3)"
  }
}

Actual Behavior

Even if the resource block for the snowflake table "table_2" is changed the terraform plan running on the changed code shows no changes. Terraform does not recognize that there should be a change on the data type of the column.

Steps to Reproduce

Copy the following configuration

resource "snowflake_database" "this" { name = "TEST_DATABASE" }

resource "snowflake_schema" "this" { database = snowflake_database.this.name name = "TEST_SCHEMA" is_transient = "false" with_managed_access = "false" data_retention_time_in_days = 1 }

resource "snowflake_table" "table_1" { database = snowflake_database.this.name schema = snowflake_schema.this.name name = "TEST_TABLE_V1" data_retention_time_in_days = 1 change_tracking = false

column { name = "ID" type = "NUMBER" }

column { name = "NAME" type = "VARCHAR(3)" } }

resource "snowflake_table" "table_2" { database = snowflake_database.this.name schema = snowflake_schema.this.name name = "TEST_TABLE_V2" data_retention_time_in_days = 1 change_tracking = false

column { name = "ID" type = "NUMBER(11,2)" }

column { name = "NAME" type = "VARCHAR(255)" } }

Run terraform apply to a Snowflake Account
Change the resource block "snowflake_table" "table_2" like this:

resource "snowflake_table" "table_2" { database = snowflake_database.this.name schema = snowflake_schema.this.name name = "TEST_TABLE_V2" data_retention_time_in_days = 1 change_tracking = false

column { name = "ID" type = "NUMBER(11,2)" }

column { name = "NAME" type = "VARCHAR(3)" } }

Run terraform plan
You will see no changes in the terraform plan which is not correct

How much impact is this issue causing?

High

Logs

No response

Additional Information

It would be great if you could provide us with an estimation when this issue could be fixed. We tested around with various provider versions and found out that this issue appears the first time in version "0.90.0". In version "0.89.0" the terraform plan showed changes as expected.

We plan to have huge changes during the next three weeks. If it is not possible to provide a hotfix we need to downgrade our current terraform project. Thanks for your help!