According to this issue and the this PR, the expected behaviour of Terraform plan/apply output after the first time, updates on schema should be ignored if string_attribute_constraints is present.
Actual Behavior
I am still seeing those triggers updates on aws_cognito_user_pool and it fails with the following output error message.
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.
Terraform Core Version
1.8.3
AWS Provider Version
5.54.1
Affected Resource(s)
aws_cognito_user_pool
Expected Behavior
According to this issue and the this PR, the expected behaviour of Terraform plan/apply output after the first time, updates on schema should be ignored if
string_attribute_constraints
is present.Actual Behavior
I am still seeing those triggers updates on
aws_cognito_user_pool
and it fails with the following output error message.Plan Output
Apply result
Relevant Error/Panic Output Snippet
No response
Terraform Configuration Files
Steps to Reproduce
Terraform apply for a template contains schemas like above twice. The second apply always fail.
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
None