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

Description

A group definition with an allocation that matches the ICD instance should not result in a change during terraform plan

The following configuration adds a group definition with a memory allocation that matches the current allocation of a databases-for-postgresql instance

resource "ibm_database" "postgresql" {
  name              = "coolguy-pg"
  plan              = "standard"
  location          = "us-south"
  service           = "databases-for-postgresql"
  resource_group_id = data.ibm_resource_group.group.id

  group {
    group_id = "member"
    
    memory {
      allocation_mb = 1024
    } 
  }
}

This results in a change reported during terraform plan

  # ibm_database.postgresql will be updated in-place
  ~ resource "ibm_database" "postgresql" {
        id                      = <crn>
        name                    = "coolguy-pg"
        # (16 unchanged attributes hidden)

      + group {
          + group_id = "member"

          + memory {
              + allocation_mb = 1024
            }
        }

        # (1 unchanged block hidden)
    }

Plan: 0 to add, 1 to change, 0 to destroy.

Applying this change will result in a noop, but the expected behavior is to report no change i.e.

No changes. Your infrastructure matches the configuration.

New or Affected Resource(s)

• ibm_database

Potential Terraform Configuration

References