Open Shomari opened 2 years ago
Initial fix addressed part of this. Additional documentation to describe high level approach for migration of user pool.
I have updated the cli to the newest version, but I still get the error. I have sent a diagnostic report. Project ID: 5c8c983e49b7f9ef7d272af952c0ad21
What's the latest on this? We've hit this issue.
Similar to @Shomari, @dbeck121 , and @djsjr, our deployed user pool, cli-inputs.json
, and the #current-cloud-backend cloudformation JSON are all in sync as far as the requiredAttributes go (and other user pool config as far as I can tell).
As with @Shomari , it only manifested when we did amplify add analytics
.
The issue occurs in amplify CLI 10.3.1 (downgrading to 7.6.8 gives us the same error).
amplify diagnose --send-report
gives: Project Identifier: 85116e8e08029dc0bc4466b8b6573fec
.
Below are our cli-inputs.json
and root-cloudformation-stack.json
.
(aside: This in our CloudFormation Template looks very suspect but I think it's unrelated: "dependsOn": "[object Object],[object Object],[object Object]",
)
My amplify/backend/auth/bpedsysauth/cli-inputs.json
:
The relevant part of my amplify/#current-cloud-backend/awscloudformation/build/root-cloudformation-stack.json
:
OK this still happens if I do nothing else other than change the order of requiredAttributes
in cli-inputs.json
from:
"requiredAttributes": ["name", "email"]
to:
"requiredAttributes": ["email", "name"]
I have the same problem after upgrading the Amplify cli from 9.2.1 to 10.4.0. Please help. Project Identifier: 8917f531808b98396e5b186f78b710ba
I am also still getting it on 10.4.0. It seems not much is happening on this issue.
Hi team @josefaidt @Straubulous any updates on this issue, my team is blocked for almost two weeks now with this error. I have sent my project my project identification number: 8917f531808b98396e5b186f78b710ba. I have read through the whole discussions and none of the suggestions worked. Thanks
Not currently feeling the "Customer Obsession" here.
I have talked for more than 10 engineers at aws support team and they haven't solved this issue, paying for more than 400 USD.
AWS support does not work.
Hi @cuneen @gorjant
I check your project Identifier.
Lets say your current required attributes are : [ 'email' , 'name'].
when upgraded to v7.3 to v7.6.9 due to a bug this required attributes in cfn changes to [ 'name'] which is a successful deployment.
After upgrading to version > v7.6.9 , amplify changes your required attributes back to normal which was previous : ['email' , 'name']. This deployment will result in same error Invalid AttributeDataType input, consider using the provided AttributeDataType enum.
Can you try to push by changing your cli-inputs.json and parameters.json to specific requited attribute which is [ 'name'] ?
As an example: Current cli-inputs.json requited attributes: [ 'email' ,'name']
Change to cli-inputs.json requited attributes: [ ''name'] ;
Change parameters.json requited attributes: [ ''name'] ;
amplify push ( this should change schema section is user pool to only name attribute)
Let me know if these steps works for you ?
@owboateng
Your problem seems different by looking at project. Can you try removing userNameCaseSensitive
field from cli-inputs.json and try to push again ?
Let me know if this works for you ?
Hi @akshbhu thanks for looking into this; We can't push right now as AWS Premium Support engineers are looking into this for us, but we did previously try what you described (based on @johnpc's comments above) and we still encountered the error.
Can you tell me which comment is this ?
I reproduced the issue with creating an amplify project with v4.5.x and upgrading to v7.3.0 ( which has the bug in required attributes) (up till here push works fine )and after than upgrading to v10.5.1. I received similar error as above, which got resolved based on my comment above
Hi @akshbhu I don't think the message you're quoting was in this thread?
Can you tell me which comment is this ?
I reproduced the issue with creating an amplify project with v4.5.x and upgrading to v7.3.0 ( which has the bug in required attributes) (up till here push works fine )and after than upgrading to v10.5.1. I received similar error as above, which got resolved based on my comment above
Hi @cunneen
Apologies for being unclear.
When you mentioned :but we did previously try what you described (based on @johnpc's comments above) and we still encountered the error.
I was trying to confirm which comment was it in this thread.
Also this is my investigation on this issue : I reproduced the issue with creating an amplify project with v4.5.x and upgrading to v7.3.0 ( which has the bug in required attributes) (up till here push works fine )and after than upgrading to v10.5.1. I received similar error as above, which got resolved based on my comment above
Hi @akshbhu , sorry for misunderstanding earlier. AWS support resolved this for us; it looks like their resolution was similar to what you suggested as our cli-inputs.json
file now only has ["name"]
.
We're no longer encountering this issue; we're on v10.8.1 .
I used @julienlaurent-migso solution and it worked.
went to the cli-inputs.json
and inserted a newline then amplify push
, which deployed properly.
Before opening, please confirm:
How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
14.17.3
Amplify CLI Version
7.6.5
What operating system are you using?
mac
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes made
Amplify Categories
auth, analytics
Amplify Commands
push
Describe the bug
I can't push changes from amplify cli or deploy code. I am always getting error " Invalid AttributeDataType input, consider using the provided AttributeDataType enum. (Service: AWSCognitoIdentityProviderService; Status Code: 400; Error Code: InvalidParameterException"
Expected behavior
I should be able to make changes and have my builds complete
Reproduction steps
Added analytics to an already existing project that had auth and api I believe this made some changes to my user pool but not exactly sure what it did. Now I can't build or push new changes
GraphQL schema(s)
Log output
Additional information
exact same issue as https://github.com/aws-amplify/amplify-cli/issues/2309 but it appears this has come back. Also seems like some else is having the same issue but they closed their issue https://github.com/aws-amplify/amplify-cli/issues/9510