system_tags on oci_core_volume triggers a modification request every time

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 "me too" comments, 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 and Provider Version

Terraform v1.3.6 on linux_amd64

provider registry.terraform.io/hashicorp/oci v5.4.0

Affected Resource(s)

affected_resources = oci_core_volume

Terraform Configuration Files

resource oci_core_volume test {
  availability_domain = "ad1"
  compartment_id =  oci_identity_compartment.cmp-test.id
  display_name = "bv-test"
  size_in_gbs = "70"
}

Debug Output

Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
  ~ update in-place

Terraform will perform the following actions:

  # oci_core_volume.test will be updated in-place
  ~ resource "oci_core_volume" "test" {
        id                  = "ocid1.volume.AK01607874.u02.6 ... ... ... 5ar65cd"
      + system_tags         = (known after apply)
        # (10 unchanged attributes hidden)
    }

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

Panic Output

Expected Behavior

Actual Behavior

Every terraform run results in a modification. Adding system_tags to lifecycle { ignore_changes = [system_tags] } doesn't help. Still triggers the modification request though.

Steps to Reproduce

Run terraform apply once to create the block volume Run terraform apply again - this should not result in any modification.

Important Factoids

We run terraform /OCI provider against a Oracle Private Cloud Appliance (PCA).

oracle / terraform-provider-oci

system_tags on oci_core_volume triggers a modification request every time #1923