random_string function makes nose in the plan exposing the ID and override_special ""

[chanakanissanka]

Terraform CLI and Provider Versions

Hi Team,
Since the last version dropped, i.e. 3.4.2, our plan shows a noise [+override_special: "" ] with exposed random string. We don't use this option.
I have reverted to 3.4.1 and don't see this noise anymore normal as it supposes to be. I just want to understand why this is happening.

Terraform Configuration

our config is simple as this
resource "random_string" "base" {
  length  = 4
  special = false

}

Expected Behavior

don't want to see an additional noise on the plan with random strings and exposed random string characters

Actual Behavior

we can see this type of noise. This is just a sample and a bunch like this where this is used.

Steps to Reproduce

N/A ( Normally, since last 2nd, every TF plan shows this. )

How much impact is this issue causing?

Medium

Logs

No response

Additional Information

No response

Code of Conduct

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

[bflad]

Hi @chanakanissanka 👋 Thank you for raising this and sorry you ran into trouble with it.

The planned fix for the override_special attribute in the random_password and random_string resources, #312, is already merged and will be released sometime in the next day or so. Once that version is released, this attribute should not show the unexpected plan difference with override_special (unless it is applied with version 3.4.2, in which the upcoming release will show another plan to fix it back to null where it should remain stable again).

[chanakanissanka]

Thanks, @bflad, for the update. look forward to the merge. Cheers

[bflad]

Hi folks 👋 Version 3.4.3 of the provider was released and should resolve some of these cases. If you are still having trouble after upgrading, please reach out in a new issue and we can take a fresh look. Thanks.

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