Fix update behavior for Cognito User Pool Clients #5478
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #5029
Changes proposed in this pull request:
UpdateUserPoolClient
API call appears to require a full specification of the client. Currently the provider sends a partial specification, including only the fields that have changed. As a result, any fields that aren't being updated are wiped out byterraform apply
. This PR changes the provider to always send a full specification based on the Terraform config.Output from acceptance testing:
The newly added acceptance test
TestAccAWSCognitoUserPoolClient_allFieldsUpdatingOneField
passes here but fails on the master branch. The failure on master looks ilke: