Artur Sawicki

Hey @murarustefaan, as I understand it, this is not an issue with the provider directly but rather with the underlying SDK, right? If so, please keep in mind that the...

Hey @JESCHO99. Thanks for reaching out to us. We have already seen a bunch of use cases where the unsafe_execute was leveraged, not only for the purposes it had been...

That's a good pointer. I will add this change to the docs in one of my PRs so that it is gone with the next release.

Hey @tmnd1991. Thanks for reaching out to us. We will address this issue during upcoming stream redesign (https://github.com/Snowflake-Labs/terraform-provider-snowflake/blob/main/ROADMAP.md#preparing-essential-ga-objects-for-the-provider-v1). I will add this issue to the list of know issues.

Hey @AaronCoquet-Easypark. Thanks for reaching out to us. Can you please share the logs from the crash? The provided logs above show only the plan output and not the result...

Hey @wesleyhillyext. Thanks for reaching out to us. We have planned to discuss this issue with the schema resource rework as part of https://github.com/Snowflake-Labs/terraform-provider-snowflake/blob/main/ROADMAP.md#preparing-essential-ga-objects-for-the-provider-v1. A few comments from my side:...

> So I didn't understand why our use of managed-access schemas might clash with the point of the PUBLIC schema – is there some other purpose implied for the PUBLIC...

Hey @wesleyhillyext. Thanks for your thoughts. TBH for me it's not a big difference if we add a boolean option to the `snowflake_database` resource which, if enabled, causes it to...

Hey @wesleyhillyext. We want to avoid dropping the PUBLIC schema programmatically (mainly because of the reasons discussed above), so we explored the non-dropping solutions. Ultimately, we will replace it with...

TL;DR We will add `drop_public_schema_on_creation` flag to the database resource in one of the upcoming versions. My answers below (not to leave the questions unanswered). > This is effectively equivalent...