[❄️ Snowflake Official] The removal of deprecated grant resources #2736
Replies: 3 comments 2 replies
-
This is likely the most hostile change I have ever seen on a project towards users. Why have you made it more difficult for people who actually use your project? |
Beta Was this translation helpful? Give feedback.
-
Agreed that this is an extremely challenging set of changes to migrate past. Especially frustrating are some of the other changes that appear to be resource name changes for no purpose other than the rename. All of these changes require a tremendous amount of downstream work which Snowflake appears to be trivializing. State changes are easy to describe in a doc, but scale ver poorly, especially in large deployments. Very disappointing to see in a previously stable terraform provider. |
Beta Was this translation helpful? Give feedback.
-
It would be useful if you could publish, for each deprecated resource, which resource one is supposed to use instead. Perhaps you have already published that somewhere, if so please could you provide a link to it? |
Beta Was this translation helpful? Give feedback.
-
Hey, as you may have already seen in other threads, we announced that with the latest release we concluded grants redesign (more details).
During the grants redesign, we introduced a new set of resources that were made to fully replace the old grant resources. Right now, we don't support deprecated resources and recently we closed all the GitHub issues opened for the deprecated grant resources. As there's an alternative for every deprecated grant resource, we decided to remove the deprecated ones on June 26, 2024 (Wed). You still will be able to use the old grant resources afterward, but only with the older provider versions. Although this will be possible, we always recommend upgrading to the latest provider version as it's the most stable one containing more features, edge cases covered, and bugs resolved. The removal is only about grant resources, every other deprecated resource is planned to be removed in the next major version release (v1.0.0). To support the migration, we recently published a resource migration guide that describes the process of "no downtime" migration with the help of state manipulation tools.
We are looking forward to hear your thoughts. In case of any errors during the migration, please open a GitHub issue.
Here's the list of resources that we're planning to remove:
Beta Was this translation helpful? Give feedback.
All reactions