[Enhancement]: hash AWS SSM Secret manager sensitive data

[Azmah-Bad]

Description

• the resource used to create a secret manager version is aws_secretsmanager_secret_version which contain the following sensitive attributes secret_string and secret_binary
• These attributes are then stored in plain text in the state file, which can be problematic
• Since these attributes force a recreation of the resource there no point of keeping the whole JSON of aws secret version
• This can be fixed easily by hashing sensitive data before storing it in the state file, and then when comparing the data to check for update only compare hashes

Affected Resource(s) and/or Data Source(s)

• aws_secretsmanager_secret_version

Potential Terraform Configuration

No response

References

No response

Would you like to implement a fix?

Yes

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