[Bug]: Table Column Updates are not recognized by Terraform Provider about terraform-provider-snowflake HOT 5 OPEN

Hey @JESCHO99. Thanks for raising this issue.

Unfortunately, this is a known error that affects multiple resources, not only tables (e.g., check #2735).

Long story short: data types with arguments (like VARCHAR(3) and VARCHAR(200)) are not always handled properly. In this case, they are both synonymized to check if the type changed, but their length is not taken into consideration, so the diff is suppressed incorrectly.

We should start working on procedures and functions next week, so the datatype topic will be addressed then. Before that, we can add a hotfix to handle properly at least changes to VARCHAR length in the table resource. The hotfix won't make it probably into the next release (tomorrow or on Friday) but should be ready next week.

from terraform-provider-snowflake.

I will also make sure it's added to the known issues/limitations in our FAQ (https://github.com/Snowflake-Labs/terraform-provider-snowflake/blob/main/CREATING_ISSUES.md#commonly-known-issues).

from terraform-provider-snowflake.

Hey @sfc-gh-asawicki, thanks for the reply. A Hotfix for Varchar Fields in the next week would help a lot. If possible it would be great if NUMBER fields could be added to the Hotfix too. Those are the two data types mainly used in our environments. Thanks for your help!

from terraform-provider-snowflake.

Hey @JESCHO99. I think we can include numbers, too; I will confirm next week.

from terraform-provider-snowflake.

Hey @JESCHO99.

I have prepared a fix both for text and number columns in #3020. It will be released as part of v0.95.0 today or tomorrow (we have to wrap a few other pull requests before making the release).
Please check the migration guide for the description of the changes and report any problems with this hotfix.

from terraform-provider-snowflake.