-
Notifications
You must be signed in to change notification settings - Fork 9.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: The terraform-provider-aws_v5.73.0_x5 plugin crashed! when applying changes to aws_cognito_user_pool resource #39992
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Similar #39823 |
Thanks for reporting this. I am facing the same issue. I created a custom attribute in the Cognito console ( Plan
Config
Error
|
Same error in
|
same issue happens on plugin version 5.75.0. |
@finkinfridom Strangely, after diving deeper into the AWS documentation I realised that it was more to do with the fact that with the aws_cognito_user_pool resource schema, attributes can be added, but not modified or removed. For my specific issue this bug relates more to the fact that an explicit error message needs to be added, to let it be known that this is an inherent characteristic with user pools. I had to remove the entire user pool and build it again without that specific user schema attribute specified. In you problem that you posted, are you also trying to modify the set schema attributes of the user pools you are deploying/configuring? |
From what I can see, the terraform plan always shows me a change in the user pool even if no changes are performed. So indeed it's trying to change something in the schema that want to reapply. |
Same problem here, after added an schema for a custom attribute. I know that I can't change a schema, but for some reason Terraform is not dealing well with this and now with this bug I cannot modify anything in my pool. |
@camilocosta a very hacky workaround would be to replicate the exact user pool schema configuration in your terraform, at the very least it won't recognise any changes and you can continue modifying other parts of your user pool. Hopefully this gets fixed soon! |
Thanks @Mehmet-Kalich , it works! |
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. |
This functionality has been released in v5.77.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
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. |
Terraform Core Version
v1.9.8
AWS Provider Version
v5.73.0
Affected Resource(s)
only the aws_cognito_user_pool resource
Expected Behavior
as there were some out of state changes made in the AWS cognito console to the schema of a user pool, the terraform was applied to bring the user pool back into state with the configured terraform.
Actual Behavior
Instead an error returned saying "Plugin did not respond" which mentions:
Error: The terraform-provider-aws_v5.73.0_x5 plugin crashed!
Relevant Error/Panic Output Snippet
Terraform Configuration Files
Steps to Reproduce
Debug Output
No response
Panic Output
No response
Important Factoids
note: the error message does not appear on a terraform plan
References
No response
Would you like to implement a fix?
Yes
The text was updated successfully, but these errors were encountered: