[❄️ Snowflake Official] Upcoming upgrade to existing resources (v0.93.0) | Need for migrating state

[sfc-gh-sthyagaraj]

As we complete the process of updating functionality and stabilizing existing resources, we’d like to enable them for the community. Our recommendation is that the community switch to the new version of the resources immediately to benefit from the update.

Benefits of immediate use of the new version of the resource

• Migration of state to the redesigned resources will need to be performed on or before the provider reaches v1. Rather than a big-bang migration, a staggered approach to moving state when new versions of resources are available allows for careful adoption, time to test, and fewer risks to mitigate

What is the roadmap for the updated resources?

• First redesigned resources will be released with v0.93.0 and will contain at least database, security integrations, and warehouse resources/datasources redesigned. Each new release will contain a few resources and will be communicated in the release notes
• NOTE that these resources should seldom see an upgrade after this release and before v1, unless critically needed (this includes the current identifiers rework)

What does this mean tactically?

• To make the transition smoother for the v1 we would keep the existing name for the redesigned resource
  • _old suffix will be added to old resource (if needed; some resources can be just migrated without the previous version left - described in detail below)
• Always check the migration guide before bumping the provider version. This is even more important now because of the upcoming breaking changes in the resources
• Anticipated changes
  • Some resources can be split into multiple ones; in such a case we will
    • Leave the old resource with suffix _old; if you want to bump the provider version and use the old resource you still have to remove the resource from the state and import it in the _old resource (following migration guide)
    • Provide new resources with more narrow capabilities (e.g. snowflake_database -> snowflake_database, snowflake_secondary_database, snowflake_shared_database). To use them without destroying the objects you need to follow migration guide
  • Some resources will not be split but will require more rework. In such cases, we will use the same approach as described above (with the suffix _old)
  • Some resources will not need bigger changes. In such cases, we WON’T provide the _old resource. For these resources, it may be enough to apply changes in the config (always check the migration guide before bumping the provider version) and let terraform apply the automatic state upgraders provided

Will the old resource exist?

• They will be available still in the older versions of the provider
• Deprecated old resource will be removed with v1 release at the latest. They will be marked as DEPRECATED in the documentation

Example migration of state

• Example here, but check the migration guide as well

Next Steps: We are always here to help you in your migration journey

• Please assess your impacts due to this upcoming change and prepare for migration
• If you believe that this will severely disrupt your business as usual activities, please let us know