"snowflake_database" "with_replication" { is not setting up the replication

[sgupta-01]

Provider Version

0.69.0

Terraform Version

v1.5.5

Describe the bug

resource "snowflake_database" "with_replication" {
name = "testing_2"
comment = "test comment 2"
replication_configuration {
accounts = ["test_account1", "test_account_2"]
ignore_edition_check = true
}
}

is not setting up the replication it's creating db's but not the replicated one

Expected behavior

A clear and concise description of what you expected to happen.

Code samples and commands

Please add code examples and commands that were run to cause the problem.

Additional context

Add any other context about the problem here.

[jreslock]

I am seeing this issue using 0.67.0 of the provider. My DB is created but the replication settings are not present.

[brandocomando]

Also seeing this in 0.70.1

[DustinMoriarty]

I am seeing this in 0.72.0. After reviewing the logs with the INFO level turned on, I found that only the CREATE DATABASE statement ran without any parameters for replication. No additional ALTER DATABASE statement was run to enable replication.

[snyker-nb]

Seeing this as well. It appears to have been introduced in 0.66.0 with the refactoring done in #1840. It looks like the replication config is now only considered for databases created from shares. A subsequent update to the database resource in TF (i.e., modify the replication_configuration) will cause the replication config to be created, but there is also a bug in the update path. It expects the ignore_edition_check to be at the root of the schema, instead of nested inside the replication_configuration key. This causes a nil pointer dereference.

[chrisluedtke]

I suspect this will be fixed by this recent PR? #2421

[sfc-gh-asawicki]

Hey @chrisluedtke. It should be fixed partly (the ignore_edition_check and nil dereference should be fixed). The mentioned PR is not fixing the creation of replicated database (but the mentioned by @snyker-nb workaround should work).

[sfc-gh-asawicki]

Hey @sgupta-01 @jreslock @brandocomando @DustinMoriarty @snyker-nb @chrisluedtke. We have released the fix as part of v0.87.0 release. Please follow the migration guide during the update. Please confirm that the issue is resolved in the newest version. Thanks!