[Bug]: 2024_08 breaks snowflake_managed_account

[jrobison-sb]

Terraform CLI Version

v1.10.0

Terraform Provider Version

v1.0.3

Company Name

Springbuk

Terraform Configuration

resource "snowflake_managed_account" "reader" {
  for_each       = length(var.snowflake_reader_accounts) > 0 ? toset(var.snowflake_reader_accounts) : []
  name           = upper("${var.env_name}_${each.key}")
  admin_name     = "admin"
  admin_password = "redacted"
  type           = "READER"
  comment        = "${var.env_name} reader account for ${each.key}"
}

Category

category:resource

Object type(s)

resource:managed_account

Expected Behavior

This resource was created a long time ago and was working fine for a long time. My expectation is that it should continue working fine without breaking terraform plan and/or terraform apply.

Actual Behavior

The actual behavior is that it does break terraform plan and it does break terraform apply, probably after BCR 2024_08 was released to general availability (at least for us).

$ terraform plan
...
│ Error: giving up after 5 attempts
│ 
│   with module.sandbox4_application.snowflake_managed_account.reader["foo"],
│   on ../../modules/aws/application/snowflake.tf line 1854, in resource "snowflake_managed_account" "reader":
│ 1854: resource "snowflake_managed_account" "reader" {

Steps to Reproduce

1. Use a snowflake_managed_account resource similar to what is seen above, and use it without BCR 2024_08. This will work fine.
2. Enable BCR 2024_08.
3. Try a terraform plan and see that it is broken.
4. Disable BCR 2024_08
5. Try a terraform plan and see that it works again

How much impact is this issue causing?

High

Logs

No response

Additional Information

I'm hesitant to post thousands of lines of TF_LOG=DEBUG, because I don't want to risk exposing secrets, but I was able to pick out this part from a debug plan log:

2025-02-12T09:57:55.910-0500 [DEBUG] provider.terraform-provider-snowflake_v1.0.3: 2025/02/12 09:57:55 [DEBUG] sql-conn-query: [query SHOW MANAGED ACCOUNTS LIKE 'SANDBOX4_FOO' --terraform_provider_usage_tracking {"json_schema_version":"1","version":"v1.0.3","resource":"snowflake_managed_account","operation":"read"} err <nil> duration 164.556417ms args {}] (LOC1234)
2025-02-12T09:57:55.910-0500 [DEBUG] provider.terraform-provider-snowflake_v1.0.3: 2025/02/12 09:57:55 [DEBUG] retryable operation resulted in error: object does not exist
2025-02-12T09:57:55.911-0500 [DEBUG] provider.terraform-provider-snowflake_v1.0.3: 2025/02/12 09:57:55 [INFO] operation not finished yet, retrying in 3 seconds

Would you like to implement a fix?

• Yeah, I'll take it 😎

[sfc-gh-jmichalak]

Hi @jrobison-sb 👋

This is similar to #3161. The issue occurs because of a renamed column in SHOW MANAGED ACCOUNTS. For now, please disable the bundle or use the execute resource. We should be able to fix this and release it soon.

[natashamathur]

Hi! Do you have a timeline for when the fixed release will come out? Trying to get an idea of in the next 1-2 weeks vs 1 month from now

[sfc-gh-jcieslak]

Hey @natashamathur 👋
The fix will be most likely released next week. Just a note, the fix will be only available in the latest version (that will be v1.0.4), so upgrade will be needed.

[natashamathur]

That's fine, we will update to 1.0.4. Thank you!

…

On Thu, Feb 13, 2025 at 9:47 AM Jan Cieślak ***@***.***> wrote: Hey @natashamathur <https://github.com/natashamathur> 👋 The fix will be most likely released next week. Just a note, the fix will be only available in the latest version (that will be v1.0.4), so upgrade will be needed. — Reply to this email directly, view it on GitHub <#3394 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIO2SK3I4OZO7YLJDPY3C632PSV63AVCNFSM6AAAAABW75C45KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJWHAZDIMZYGI> . You are receiving this because you were mentioned.Message ID: ***@***.*** .com> [image: sfc-gh-jcieslak]*sfc-gh-jcieslak* left a comment (Snowflake-Labs/terraform-provider-snowflake#3394) <#3394 (comment)> Hey @natashamathur <https://github.com/natashamathur> 👋 The fix will be most likely released next week. Just a note, the fix will be only available in the latest version (that will be v1.0.4), so upgrade will be needed. — Reply to this email directly, view it on GitHub <#3394 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIO2SK3I4OZO7YLJDPY3C632PSV63AVCNFSM6AAAAABW75C45KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMNJWHAZDIMZYGI> . You are receiving this because you were mentioned.Message ID: ***@***.*** .com>

-- Natasha Mathur Director of Data *Calendly <https://calendly.com/natashamathur/30-minute-meeting>* Technology Advancing Primary Care

[spcvalente]

same here, looking forward to that release. cheers!

[alexandrewatercare]

Hi,

Do we know when it'll be fixed, it become a blocker for our delivery.

Thanks

[sfc-gh-asawicki]

We should have a release next week (Tue or Wed).

[ldonnellanIDBS]

Thank you for fixing this. It seems to be getting quite close to the scheduled time for 2024_08 getting Generally Enabled. We've currently got that bundle disabled as a workaround while this is being resolved. Do you have an idea of when in March that will be happening and how quickly we'll need to action moving to 1.0.4?

For reference: https://docs.snowflake.com/en/release-notes/bcr-bundles/2024_08_bundle

[spcvalente]

1.0.4 fixed the issue

[sfc-gh-jcieslak]

Hi all 👋
The 1.0.4 was released yesterday. @spcvalente Thanks for confirming. @jrobison-sb as you are the author of this issue, could you also confirm and close the ticket (or leave it open if there's still some issues with managed account)?

[ldonnellanIDBS]

Thank you for fixing this. It seems to be getting quite close to the scheduled time for 2024_08 getting Generally Enabled. We've currently got that bundle disabled as a workaround while this is being resolved. Do you have an idea of when in March that will be happening and how quickly we'll need to action moving to 1.0.4?

For reference: https://docs.snowflake.com/en/release-notes/bcr-bundles/2024_08_bundle

For anybody wondering, I raised this with Snowflake support and got the following response:

The Bundle is expected to be made Generally Enabled in the third week of March 2025. However, this schedule is subject to change

[jrobison-sb]

@jrobison-sb as you are the author of this issue, could you also confirm and close the ticket (or leave it open if there's still some issues with managed account)?

Yes, I'll upgrade and re-enable BCR 2024_08 probably today or tomorrow and will report back. Thanks.

[jrobison-sb]

@sfc-gh-jcieslak

Hi all 👋 The 1.0.4 was released yesterday. @jrobison-sb as you are the author of this issue, could you also confirm and close the ticket (or leave it open if there's still some issues with managed account)?

I upgraded this morning and it works great. Thank you for your efforts on this one.