Prevent keepers triggering an in-place update following import

[bendbennett]

Terraform CLI and Provider Versions

Provider version: v3.4.3

Terraform Configuration

resource "random_id" "server" {
    byte_length = 4
}

resource "random_integer" "integer_1" {
    min  = 1
    max  = 3
}

resource "random_uuid" "basic" { 
}

Expected Behavior

• Importing random_id using terraform import random_id.server p-9hUg and then running terraform apply using the configuration supplied should result in a no-op.
• Importing random_integer using terraform import random_integer.integer_1 2,1,3 and then running terraform apply using the configuration supplied should result in a no-op.
• Importing random_uuid using terraform import random_uuid.main aabbccdd-eeff-0011-2233-445566778899 and then running terraform apply using the configuration supplied should result in a no-op.

Actual Behavior

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:

  # random_id.server will be updated in-place
  ~ resource "random_id" "server" {
        id          = "p-9hUg"
      - keepers     = {} -> null
        # (5 unchanged attributes hidden)
    }

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

Steps to Reproduce

1. Run the steps described in "Expected Behaviour".

How much impact is this issue causing?

Low

Logs

No response

Additional Information

No response

Code of Conduct

• I agree to follow this project's Code of Conduct

[github-actions]

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.