[Bug]: aws_ssm_parameter doesn't manage insecure_value after import

Terraform Core Version

1.6.1

AWS Provider Version

5.51.1

Affected Resource(s)

aws_ssm_parameter

Expected Behavior

Changes to insecure_value should be reflected in the resource when applied.

Actual Behavior

Plan shows an expected change, though reflected as known after apply rather than as the concrete change.

Apply doesn't affect any change of the resource.

Relevant Error/Panic Output Snippet

No errors are emitted and during the apply stage the resource is reported as `Modifying...` but no change is made.

Terraform Configuration Files

resource "aws_ssm_parameter" "param-a" {
  name        = "/shared-config/param-a"
  type        = "String"
  description = "Config for param-a"

  insecure_value = "value-a"
}

Steps to Reproduce

Create a parameter via the AWS console
Import the parameter with terraform import aws_ssm_parameter.param-a /shared-config/param-a
Make a change to the value in the terraform code
Plan and apply the terraform
View the parameter in the AWS console and notice that no change was made

Debug Output

No response

Panic Output

No response

Important Factoids

After import - the state contains insecure_value = null and the value is stored in the value field.

hashicorp / terraform-provider-aws

[Bug]: aws_ssm_parameter doesn't manage insecure_value after import #37733