Closed harukitake closed 7 months ago
Hey @harukitake. Thanks for reaching out to us.
We marked the direction
deprecated but we did not remove the forceNew or added any diff suppresion for this parameter. The reason was, that this is just a deprecation warning. We've already learned that our users do not like the warning messages. Because of that:
What you can do now:
Thanks. I will do this and wait for update.
Leave direction without change (you will see warnings) and wait for the version with the aforementioned changes.
Hey @harukitake. We released the fox as part of 0.86.0 release. Could you please check if this solves the issue for you?
@sfc-gh-asawicki Thanks for quick fix.
It has resolved.
No changes. Your infrastructure matches the configuration.
Great to hear that. I'm closing the issue then.
Terraform CLI and Provider Versions
Terraform Configuration
before
after
Expected Behavior
NO changes
Actual Behavior
Steps to Reproduce
terraform apply
How much impact is this issue causing?
Medium
Logs
No response
Additional Information
I removed a parameter that became deprecated due to a version upgrade of the Terraform provider, expecting no change in behavior. However, an unexpected diff appeared. Is this a bug? If not, please advise on how to handle it.
I read https://github.com/Snowflake-Labs/terraform-provider-snowflake/blob/main/MIGRATION_GUIDE.md#snowflake_notification_integration-resource-changes