-
Notifications
You must be signed in to change notification settings - Fork 9.1k
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]: "Provider produced inconsistent result after apply" in aws_cognito_user_pool_client #30268
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Seeing same, provider update to 4.60 broke compatibility for all existing Cognito clients, giving unexpected new value error for attributes Checked, downgrading to 4.59 allows to apply with no error |
Related: #30257. |
Worked for me forcing provider <= 4.59 as @alnemo mentioned |
same issue here when I have: explicit_auth_flows = [] |
I have the same issue when I have empty callback URLs e.g.: callback_urls = [] |
Fixed by #30459 |
This functionality has been released in v4.62.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! |
Hi, it still seems to give an error. I am using tf core 1.4.2 and aws provider 4.62.0.
Anything I could try? Downgrading aws provider to 4.59.0 does not show this issue. |
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
1.1.7
AWS Provider Version
~> 4.55
Affected Resource(s)
Expected Behavior
apply
should have succeededActual Behavior
Terraform output the error message provided below. It looks like an "empty list vs null" issue.
Relevant Error/Panic Output Snippet
Terraform Configuration Files
Steps to Reproduce
I'm not sure it is feasible to reproduce a full Cognito setup. The "null vs empty list" issue can probably easily be checked in the backing code.
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
No response
Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: