-
Notifications
You must be signed in to change notification settings - Fork 250
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
CongitoUserPool does not update successfully on deploy #617
Comments
I am also having this issue |
Oh interesting. Thanks for the pointer. |
In my case it turned out, that I created the CognitoUserPool and afterwards modified some configuration of it which affected already created schema attributes. This does not work by design in a Cognito User Pool. My solution was to remove and recreate the CognitoUserPool. Be careful with the attributes. |
Still experiencing this error almost in every deployment (in version
What do You think about adding the temporary "fix" till #621 is resolved?
|
Nevermind, it seems that the upstream issue has been closed/fixed: |
Same issue in sst 0.0.535 |
Can you try the latest? If they've released it then we should have it too. |
It looks to be working for me now. |
Nice |
Working for me too! thanks! |
When adding a sst.aws.CognitoUserPool, the sst deploy will run successfully on the first deploy but fail on an update with the following error.
here is an example sst.config.ts
Please note that the same error occurs with the pulumi aws.cognito.UserPool resource but it can be worked around by adding the
ignoreChanges: ["schemas"]
option. Currently, the sst construct does not pass the options to the pulumi resource so this work around does not work for sst.My suggestion would be to support the options on the sst construct as it will likely be useful in other cases as well.
sst ion version: 0.0.473
The text was updated successfully, but these errors were encountered: