-
Notifications
You must be signed in to change notification settings - Fork 819
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
Error 'Existing schema attributes cannot be modified or deleted' in 'amplify push' following 'amplify update auth' #13160
Comments
Amplify CLI might be right repo for this issue. Transferring this issue to Amplify CLI repo |
Hey @ankpshah, thank you for reaching out. The issue appears to be similar to #13095 and #12827. Was the Amplify CLI upgraded from version before 7.x? If yes, could you try adding the attributes using the override functionality by running |
@rayshi67 could you check the environment stack in Cloudformation console for any error in the events? |
I deleted a couple of old environments yesterday before doing a clone, and I can see all deletes are completed successfully on Cloudformation console. I cannot see any relevant error there. There was no error occurred using 'amplify add env' and 'amplify push' earlier. But we need the clone to work otherwise we would have to write migration scripts now I tried again to clone the existing env today, and got back the same error, |
Hey @rayshi67, wanted to get some additional information in using the clone mechanism in the AWS console? |
So what is the root cause of the error when doing the clone in Amplify console? Without using the clone in Amplify console, how could we back up the Amplify environment including its data? And if we use ‘amplify env add’ to spin a new env, how would the data in cognito, dynamodb, and s3 etc in existing amplify env get populated into the newly created env? At the moment we haven’t got any mechanism in place for achieving that. So it would be great if you could point us to the right direction. |
@rayshi67 thank you for the information. The clone functionality in the AWS Amplify console is similar to |
wanted to provide an update on this issue, I was able to reproduce the issue by diving into the logs. The clone error was occurring due to resource overrides being present in the project. I have reached out to the appropriate Amplify team regarding this behaviour. |
Thank you for the update. |
Closing the issue, please feel free in reaching out to us again. |
|
Before opening, please confirm:
Language and Async Model
Java
Amplify Categories
Authentication
Gradle script dependencies
// Put output below this line
Environment information
Please include any relevant guides or documentation you're referencing
No response
Describe the bug
I couldn't push with AWS amplify as the Auth version was too old that needs to be updated.
I did 'amplify update auth' and selected 'Apply default configuration without Social Provider (Federation)'.
However after i did 'amplify push' I got the following error:
Existing schema attributes cannot be modified or deleted. (Service: AWSCognitoIdentityProvider; Status Code: 400; Error Code: InvalidParameterException; Request ID: null; Proxy: null)
Reproduction steps (if applicable)
amplify update Auth
amplify push
Code Snippet
// Put your code below this line.
Log output
amplifyconfiguration.json
No response
GraphQL Schema
Additional information and screenshots
amplify --version
12.3.0
The text was updated successfully, but these errors were encountered: