-
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
resource/cognito_user_pool change unexpected attributes every apply
#3389
Comments
apply
apply
next
|
According to aws, the behaviour of |
Hey @atsushi-ishibashi Thanks. |
@radeksimko Sure👍
cli output
Next update tf and apply.
cli output
Expected OutcomeOnly Actual
|
The fix to properly pass all defined attributes during update of |
This has been released in version 1.32.0 of the AWS provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. |
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. If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks! |
@Ninir @radeksimko @bflad (Sorry for mentioning, but we have a serious problem with this bug🙇)
Maybe Related: #3009
Problem
Everytime you apply,
aws_cognito_user_pool.auto_verified_attributes
was removed.Reason
cognitoidentityprovider.UpdateUserPoolInput
seems to require every param if it doesn't change. So the current updates with nil and aws updates user pool with default value.(The below example is about
MfaConfiguration
)next update the same user pool
By filtering
HasChange
, everyapply
change the real resource.So far I couldn't confirm which params work in the same way...
And I couldn't understand why acceptance test catch this one 🤔 The behavior of aws has changed??
The cause may be go-sdk?
PS:
cli works the same.
Because only attributes which changed were checked.
The text was updated successfully, but these errors were encountered: