Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Lock Snowflake Terraform provider version #48

Merged
merged 1 commit into from
Sep 23, 2024
Merged

Lock Snowflake Terraform provider version #48

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion content/en/user-guide/integrations/terraform/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ terraform {
required_providers {
snowflake = {
source = "Snowflake-Labs/snowflake"
version = "~> 0.61"
version = "= 0.92"
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Having looked at Terraform Snowflake Provider it is recommended to always use the newest version as they provide limited support. As the provider is in the experimental phase, I don't think locking the version could be a good idea, at least until a stable version with backward compatibility comes out.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I understand your perspective, but I have a different view on this. Having a working example is important for users who want to experiment and get hands-on experience with the platform. If the current example doesn’t work which is the case now, it could discourage users from trying out the platform.

While both LocalStack Snowflake and the Snowflake Terraform provider are still in development, it is even more important to lock versions. Without version constraints, there’s a higher risk of introducing breaking changes from either side, which could cause further issues and confusion. Locking the version, for now, ensures a stable reference point for users until both tools mature and offer better backward compatibility.

}
}
}
Expand Down
Loading