You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Create a Cognito User Pool via classic AWS package (i.e. new aws.cognito.UserPool())
Run pulumi up
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
The text was updated successfully, but these errors were encountered:
OK thanks. So just to confirm - nothing we can do but wait til that upstream issue is fixed?
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
Hello!
Issue details
When updating AWS Cognito User Pool (i.e.
pulumi up
for the second time) without changing anything, it errors out:I also noticed that Cognito IdentityProvider resource also shows diffs, even though nothing was changed in code:
Steps to reproduce
new aws.cognito.UserPool()
)pulumi up
pulumi up
again without changing any codeExpected:
pulumi up
should complete with no changes and no errors when no code is changedActual: It errors out instead:
* error updating Cognito User Pool (us-west-1_xxxxxxxxx): cannot modify or remove schema items
The text was updated successfully, but these errors were encountered: