rdb instance state problem

[D0wn3r]

Community Note

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment

Terraform Version

Terraform v1.9.4
on linux_amd64
+ provider registry.terraform.io/hashicorp/local v2.5.1
+ provider registry.terraform.io/scaleway/scaleway v2.41.0

Affected Resource(s)

• scaleway_rdb_instance

Terraform Configuration Files

terraform {
  required_providers {
    scaleway = {
      source = "scaleway/scaleway"
      version = "2.42.1"
    }
  }
  required_version = ">= 1.1.0"
}

provider "scaleway" {
  project_id        = "replace"
  zone            = "fr-par-2"
  region          = "fr-par"
  access_key      = "replace"
  secret_key      = "replace"
}

resource "scaleway_rdb_instance" "postgresql" {
  name           = "test"
  node_type      = "DB-DEV-S"
  engine         = "POSTGRESQL-15"
  is_ha_cluster  = false
  user_name      = "test"
  password       = "Th1s_is_my_password"
}

Expected Behavior

When we apply 2 times without changes, nothing should change

Actual Behavior

Every apply make change even if our config file didn't change

Steps to Reproduce

1. terraform apply multiple times

[D0wn3r]

I found this problem is caused by the case sensitive when the state is calculated while the provider is not case sensitive to create.
POSTGRESQL-15 -> it will be created well but will trigger an update always
PostgreSQL-15 -> will be ok