How do I now generate amplify/backend/api/amplifyDatasource/build/schema.graphql

I used to run amplify codegen models to generate a full schema into amplify/backend/api/amplifyDatasource/build/schema.graphql from the one in amplify/backend/api/amplifyDatasource/schema.graphql. Newer versions of the cli no longer update this file when I run amplify codegen models, altho both versions have similar console output.

npm version that does generate this file: @aws-amplify/cli@4.17.2 npm version I am using now that doesn’t generate this file: @aws-amplify/cli@4.41.2

I am currently running a docker container with my code mounted in and the old cli installed to generate the complete schema, but it’s painful having to switch between the two versions to generate my complete schema. Has this functionality moved? Is this a bug?

[tommyvn]

ideally both but i certainly need the complete schema file separately from an amplify deployment. I don’t ship infra thru amplify, my backend has a large number of components that I don’t want managed in one place, and build and runtime mechanics that weren’t and still aren’t possible with amplify, even after the vNext stuff is stable. My team takes advantage of the annotations like @connection etc to build the schema with consistent connection object shapes for example, but the deployment is handed off to another cloudformation template that looks very little like an amplify one.

For now I will pin to the version of the amplify cli to the one where I was able to export the built schema without being forced to also deploy, and I’ll watch the issue you linked to move to that machinery for schema generation without deployment once it’s ready.

Thanks all for looking into this for me.

[github-actions[bot]]

This issue has been automatically locked since there hasn’t been any recent activity after it was closed. Please open a new issue for related bugs.

Looking for a help forum? We recommend joining the Amplify Community Discord server *-help channels for those types of questions.