-
Notifications
You must be signed in to change notification settings - Fork 427
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.
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
chore(main): release 0.95.0 #2977
Conversation
584b221
to
fb60349
Compare
Integration tests failure for 584b221db189b6640b54ded4bec5ad23fb4b11c8 |
Integration tests failure for fb60349cee17f5c9e844418cf7c77843ac7418ae |
fb60349
to
31c27bd
Compare
Integration tests failure for 31c27bda6f5e850f51238db78d10bb686c94af92 |
31c27bd
to
3b180a1
Compare
Integration tests failure for 3b180a1316e574fe422fd90a8221c006cb9cdd87 |
dbba8fc
to
87466eb
Compare
Integration tests failure for dbba8fc777acf08aff4ab250f7e69250b949ec24 |
Integration tests failure for 87466eb07470a5de3858da9c837cc7167c490454 |
87466eb
to
9786117
Compare
Integration tests failure for 97861179b9fce2b602ce98db237880e13eff7d7a |
9786117
to
b8011ce
Compare
Integration tests failure for b8011ce853e408a5f98069fbd3e4745370efe7d6 |
b8011ce
to
4bb97e5
Compare
Integration tests failure for 4bb97e5ef9efadf559b9026867242a171efacddd |
4bb97e5
to
d4f80b8
Compare
Integration tests failure for d4f80b8a145a6af7a2b40306655cb832da99e18f |
d4f80b8
to
14bf9b7
Compare
Integration tests failure for 14bf9b7e296485cbfe09625d118aa37f4537e85d |
9bdceb4
to
a61266e
Compare
Integration tests failure for 9bdceb4c5796716fddbe63a24432a99b22c92256 |
Integration tests failure for a61266e6f6beb0b0ce6f2f518952255d555668f8 |
a61266e
to
6ad47fd
Compare
Integration tests failure for 6ad47fde43467bc97d6cbab3566e5d06e54bf8e4 |
6ad47fd
to
ef3f992
Compare
8785a81
to
d79af78
Compare
Integration tests failure for d79af783a7bc7e9f187f3b5371fff19f9473d504 |
d79af78
to
5422ca8
Compare
Integration tests failure for 5422ca8233866955fb67c36c830041b154a4cf65 |
35d6a62
to
38f8f1d
Compare
Integration tests failure for 35d6a6202b3ccf8df5bb2686a5efa241a6f5d428 |
Integration tests failure for 98b7437fe5f55ff4a713bdbb7e90fa42d2ca1462 |
Integration tests failure for 38f8f1db5e0033e94a9ac8e7773a3db8a50c3afa |
Any progress on this release? |
Hey @chris-codaio. Yes, it's almost ready. Should be released today. |
38f8f1d
to
cca8bcd
Compare
Integration tests failure for cca8bcd595305fb450b9d75679c7c08a0fa85580 |
cca8bcd
to
31d0cee
Compare
Integration tests failure for 31d0cee7df3a4b1ce68749a39ef5c3feedf10faf |
31d0cee
to
1c062e2
Compare
Integration tests cancelled for 1c062e23545c4fc6bf48836f00cba7b2f5f799d8 |
Seeing an error with this release while trying to read existing
|
Hey @chris-codaio. This is expected. Please check the note in the documentation: https://registry.terraform.io/providers/Snowflake-Labs/snowflake/latest/docs/resources/view. Instead of providing the default warehouse for your tf user, you can also specify the warehouse in the connection details using https://registry.terraform.io/providers/Snowflake-Labs/snowflake/latest/docs#warehouse. |
It's also listed in the migration guide for this version: https://github.com/Snowflake-Labs/terraform-provider-snowflake/blob/main/MIGRATION_GUIDE.md#breaking-change-required-warehouse. |
My bad for missing that. Thanks for the pointers! |
No worries. We are aware that setting warehouse using the listed options is not ideal (e.g. for situations where different warehouses should be used in a single tf deployment). We will address this topic, but probably after V1. One option we consider is to have a warehouse on each particular resource (and call I will add this to the design decisions for better transparency. |
🤖 I have created a release beep boop
0.95.0 (2024-09-04)
🎉 What's new:
🔧 Misc
🐛 Bug fixes:
This PR was generated with Release Please. See documentation.