Open heathsnow opened 2 weeks ago
Voting for Prioritization
Volunteering to Work on This Issue
According to CreateTrust, the validation regex for TrustPassword
is ^(\p{LD}|\p{Punct}| )+$
, which is normalized as ^(\p{L}|\p{Nd}|\p{P}| )+$
in the Terraform code. I've tested the latter with https://regexr.com/ with the Unicode flag, and it seems that ^
is not being recognized as a punctuation by the regex - it's recognized as a symbol (\p{S}
). Thus the password r;3^d@c_t>e^(d]
fails validation. This could be an AWS documentation issue that should first be investigated to confirm the next course of action for the Terraform resource.
In my testing it appears that any of the symbols ;^@_>^(\
are causing an issue, which isn't the case in the console.
Terraform Core Version
1.5.7
AWS Provider Version
5.53.0
Affected Resource(s)
aws_directory_service_trust
Expected Behavior
trust_password should only be restricted to
May be up to 128 characters long.
Actual Behavior
trust_password is restricted to
Can contain upper- and lower-case letters, numbers, and punctuation characters. May be up to 128 characters long.
Relevant Error/Panic Output Snippet
Terraform Configuration Files
Steps to Reproduce
One-Way: Outgoing
forest trust in AWS Directory Services and use the same password.aws_directory_service_trust
fails with an error while the AWS console does not.Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
No