Skip to content
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

AWS Cognito User Pool errors out on update even though nothing is changed #1813

Closed
seunggs opened this issue Feb 6, 2022 · 4 comments
Closed
Assignees
Labels
kind/bug Some behavior is incorrect or out of spec resolution/fixed This issue was fixed

Comments

@seunggs
Copy link

seunggs commented Feb 6, 2022

Hello!

  • Vote on this issue by adding a 👍 reaction
  • To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already)

Issue details

When updating AWS Cognito User Pool (i.e. pulumi up for the second time) without changing anything, it errors out:

* error updating Cognito User Pool (us-west-1_xxxxxxxxx): cannot modify or remove schema items

I also noticed that Cognito IdentityProvider resource also shows diffs, even though nothing was changed in code:

[diff: ~attributeMapping,providerDetails]

Steps to reproduce

  1. Create a Cognito User Pool via classic AWS package (i.e. new aws.cognito.UserPool())
  2. Run pulumi up
  3. Run pulumi up again without changing any code

Expected: pulumi up should complete with no changes and no errors when no code is changed
Actual: It errors out instead: * error updating Cognito User Pool (us-west-1_xxxxxxxxx): cannot modify or remove schema items

@mikhailshilkov mikhailshilkov transferred this issue from pulumi/pulumi Feb 8, 2022
@guineveresaenger guineveresaenger added the awaiting-upstream The issue cannot be resolved without action in another repository (may be owned by Pulumi). label Feb 8, 2022
@guineveresaenger
Copy link
Contributor

Hi there! This appears to be an upstream bug:
hashicorp/terraform-provider-aws#21654

@seunggs
Copy link
Author

seunggs commented Feb 10, 2022

OK thanks. So just to confirm - nothing we can do but wait til that upstream issue is fixed?

@mnlumi mnlumi added kind/bug Some behavior is incorrect or out of spec and removed awaiting-upstream The issue cannot be resolved without action in another repository (may be owned by Pulumi). labels Jul 25, 2023
@mnlumi
Copy link

mnlumi commented Jul 25, 2023

The upstream bug has been closed. We should test to verify that this is no longer an issue. cc @mikhailshilkov

@mnlumi mnlumi self-assigned this Jul 25, 2023
@mnlumi mnlumi added the resolution/fixed This issue was fixed label Aug 3, 2023
@mnlumi
Copy link

mnlumi commented Aug 3, 2023

Verified that there is no longer an error generated with AWS 5.42.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Some behavior is incorrect or out of spec resolution/fixed This issue was fixed
Projects
None yet
Development

No branches or pull requests

3 participants