random_password Showing Unexpected Plan 3.3.2 to 3.4.2

[bflad]

Terraform CLI and Provider Versions

Terraform v1.2.7
on darwin_arm64

• provider registry.terraform.io/hashicorp/random v3.4.2

Terraform Configuration

terraform {
  required_providers {
    random = {
      source  = "hashicorp/random"
      version = "3.4.2"
      # version = "3.3.2"
    }
  }
}

resource "random_password" "test" {
  length = 20
}

Expected Behavior

No plan difference.

Actual Behavior

$ terraform apply        
random_password.test: Refreshing state... [id=none]

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_password.test will be updated in-place
  ~ resource "random_password" "test" {
        id          = "none"
        # (12 unchanged attributes hidden)
    }

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

Steps to Reproduce

1. terraform apply

How much impact is this issue causing?

Medium

Logs

No response

Additional Information

May be related to small change in #305 where override_special was having issues with framework migration testing and the fix seemed to be adding a default value plan modifier of types.String{Value: ""}. Here's the state difference after the odd plan output:

4c4
<   "serial": 1,
---
>   "serial": 3,
28c28
<             "override_special": null,
---
>             "override_special": "",
33,34c33
<           "sensitive_attributes": [],
<           "private": "eyJzY2hlbWFfdmVyc2lvbiI6IjIifQ=="
---
>           "sensitive_attributes": []

Potentially removing Computed and removing the default value plan modifier can fix this.

Code of Conduct

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

[amh-mw]

Same behavior observed this morning for random_string, 3.4.1 -> 3.4.2.

[fgm]

Same problem with random_string

[mycloud91]

Any solution/suggestion on the same? I'm also facing the same issue after upgrading the terraform azurerm version (v3.0.0).
can I safely ignore and what was the exact impact of this? whether it will reset the random password string?

[lucascantor]

@SaravananGuru pinning to 3.3.2 for the time being seems to resolve this issue for me:

terraform {
  required_version = ">= 1.2.2"
  required_providers {
    random = {
      source  = "hashicorp/random"
      version = "3.3.2"
    }
  }
}

[mycloud91]

@bflad and @lucascantor thank you for the update. Even if it updates the ID to null technically its internal terraform value does not reset the value of the random password result. so, I have safely ignored and applied the plan. It working fine as expected.

[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.