[Bug]: Ambigious terraform plan output for tls_private_key resource

[EugenKon]

Terraform Core Version

v1.8.4

AWS Provider Version

v5.51.1

Affected Resource(s)

• tls_private_key

Expected Behavior

I do not expect to see rsa_bits because I used algorithm = "ED25519" configuration option. These are two different ciphers.

Actual Behavior

Relevant Error/Panic Output Snippet

No response

Terraform Configuration Files

resource "tls_private_key" "pk" {
  algorithm = "ED25519"
}

Steps to Reproduce

1. terraform plan

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

No response

Would you like to implement a fix?

None

[github-actions]

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please see our prioritization guide for information on how we prioritize.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[justinretzolk]

Hi @EugenKon 👋 It looks like you were attempting to report an issue with the TLS provider. The repository for that provider may be found at hashicorp/terraform-provider-tls. With that in mind, I'm going to close this issue.

[github-actions]

Warning

This issue has been closed, meaning that any additional comments are hard for our team to see. Please assume that the maintainers will not see them.

Ongoing conversations amongst community members are welcome, however, the issue will be locked after 30 days. Moving conversations to another venue, such as the AWS Provider forum, is recommended. If you have additional concerns, please open a new issue, referencing this one where needed.

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