amplify add api requires "Provide a custom type name" about amplify-category-api HOT 4 CLOSED

@oste You can get rid of the type generated when editing the schema before pushing. That would make sure that a table is not generated.

from amplify-category-api.

@kaustavghosh06 I actually tried this before running amplify api add-graphql-datasource and was given this error

    at syntaxError (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/graphql/error/syntaxError.js:24:10)
    at unexpected (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/graphql/language/parser.js:1322:33)
    at parseDefinition (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/graphql/language/parser.js:152:9)
    at parseDocument (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/graphql/language/parser.js:110:22)
    at Object.parse (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/graphql/language/parser.js:38:10)
    at datasourceSelectionPrompt.then.then.then (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/amplify-category-api/commands/api/add-datasource.js:111:46)
    at processTicksAndRejections (internal/process/next_tick.js:81:5)
There was an error adding the datasource```

Will try to do that after adding the aurora data source. Thanks!

from amplify-category-api.

I am also running into this bug. I am attempting to add an existing aurora-serverless datasource with the amplify api add-graphql-datasource command. I am given this error after removing amplify's default custom type MyType and then running the command, similar to above:

GraphQLError: Syntax Error: Unexpected <EOF> at syntaxError (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/graphql/error/syntaxError.js:24:10) at unexpected (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/graphql/language/parser.js:1322:33) at parseDefinition (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/graphql/language/parser.js:152:9) at parseDocument (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/graphql/language/parser.js:110:22) at Object.parse (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/graphql/language/parser.js:38:10) at datasourceSelectionPrompt.then.then.then (/usr/local/lib/node_modules/@aws-amplify/cli/node_modules/amplify-category-api/commands/api/add-datasource.js:108:46) at <anonymous> at process._tickDomainCallback (internal/process/next_tick.js:228:7) There was an error adding the datasource

Update:
I had to work around this by letting amplify add api create a custom type MyType for me, then running amplify api add-graphql-datasource, then removing all references to MyType, and finally running amplify push. I also was getting odd errors of resources not being found, and after some digging it turned out to be amplify naming my resources incorrectly due to punctuation in my RDS schema.

Template format error: Resource name order_itemsCreateResolver is non alphanumeric.

Resource Name: auditListResolver (AWS::AppSync::Resolver) Event Type: create Reason: No field named listAudits found on type Query

So I had to go edit my MySQL schema in RDS, beginning each table name with a capital letter, and not using any non-alphanumeric characters. THEN, push could complete, and generate GraphQL operations for me in the process.

from amplify-category-api.

This issue should be addressed in your new integration with MySQL / PostgreSQL https://docs.amplify.aws/react/build-a-backend/graphqlapi/connect-api-to-existing-database/

from amplify-category-api.