FAQ

December 8, 2025 · View on GitHub

What are the current/future plans for the provider?

Our current plans are documented in the publicly available roadmap that you can find in our repository. We will be updating it to keep you posted on what’s coming for the provider.

When will the Snowflake feature X be available in the provider?

It depends on the status of the feature. Snowflake marks features as follows:

  • Private Preview (PrPr)
  • Public Preview (PuPr)
  • Generally Available (GA)

Currently, our main focus is on making the provider stable with the most stable GA features, but please take a closer look at our recently updated roadmap which describes our priorities for the next quarters.

The provider uses SQL under the hood. When requesting a new feature, make sure all the necessary SQL commands representing CRUD (CREATE/READ/UPDATE/DELETE) operations are available in Snowflake. If they are not, you can create a feature request (reach out to your account manager) for Snowflake to add the missing functionality.

When will my bug report be fixed/released?

Our team is checking daily incoming GitHub issues. The resolution depends on the complexity and the topic of a given issue, but the general rules are:

  • If the issue is easy enough, we tend to answer it immediately and provide fix depending on the issue and our current workload.
  • If the issue needs more insight, we tend to reproduce the issue usually in a matter of days and answer/fix it right away (also very dependent on our current workload).
  • If the issue is a part of the incoming topic on the roadmap, we postpone it to resolve it with the related tasks.

The releases usually happen once every two-three weeks, mostly on Wednesdays or Thursdays.

How to migrate from version X to Y?

As noted at the top of our README, the project is still experimental and breaking change may occur. We try to minimize such changes, but with some of the changes required for version 1.0.0, it’s inevitable. Because of that, whenever we introduce any breaking change, we add it to the migration guide. It’s a document containing every breaking change (starting from around v0.73.0) with additional hints on how to migrate resources between the versions.

How can I contribute?

If you would like to contribute to the project, please follow our contribution guidelines.

How can I debug the issue myself?

The provider is simply an abstraction issuing SQL commands through the Go Snowflake driver, so most of the errors will be connected to incorrectly built or executed SQL statements. To see what SQLs are being run you have to set more verbose logging check the section below. To confirm the correctness of the SQLs, refer to the official Snowflake documentation. If the SQLs seem correct, try to run them in the Snowsight to confirm it's not a Snowflake issue.

How can I turn on logs?

The provider offers two main types of logging:

  • Terraform execution (check Terraform Debugging Documentation) - you can set it through the TF_LOG environment variable, e.g.: TF_LOG=DEBUG; it will make output of the Terraform execution more verbose.
  • Snowflake communication (using the logs from the underlying Go Snowflake driver) - you can set it directly in the provider config (driver_tracing attribute), by SNOWFLAKE_DRIVER_TRACING environmental variable (e.g. SNOWFLAKE_DRIVER_TRACING=info), or by drivertracing field in the TOML file. To see the communication with Snowflake (including the SQL commands run) we recommend setting it to info.

Note: Since v2.11.0 provider version, queries are not logged by default. If you need query-level debugging, ensure you configure appropriate logging settings:

  • log_query_text - when set to true, query text will be logged
  • log_query_parameters - when set to true, query parameters will be logged

These options can be set in the provider configuration, TOML configuration file, or via environment variables. Read the documentation for more details.

Note that you still need to set the INFO level in driver_tracing field to see the query logs.

As driver logs may seem cluttered, to locate the SQL commands run, search for:

  • (preferred) --terraform_provider_usage_tracking
  • msg="Query:
  • msg="Exec:

How can I import already existing Snowflake infrastructure into Terraform?

Please refer to this document as it describes different approaches of importing the existing Snowflake infrastructure into Terraform as configuration. One thing worth noting is that some approaches can be automated by scripts interacting with Snowflake and generating needed configuration blocks, which is highly recommended for large-scale migrations.

What identifiers are valid inside the provider and how to reference one resource inside the other one?

Please refer to this document

Is this provider compatible with OpenTofu?

Although, the provider is present in the OpenTofu Registry (see), it is not currently supported. While it's mostly compatible with Terraform, OpenTofu's reactive implementation of new Terraform features based on community demand may decrease compatibility over time. We plan to research OpenTofu support in the future, but there's no timeline yet (once planned, it will appear in the roadmap). For now, you must research and assess the risk of provider incompatibility.