Gen 1 Updated Amplify CLI and getting errors on hosting push

[gakinson]

How did you install the Amplify CLI?

npm

If applicable, what version of Node.js are you using?

18

Amplify CLI Version

12.12.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.

nope

Describe the bug

We upgraded to use the latest CLI version from 10.8.X to 12.12.5 and the push works fine locally, but when we update it on the hosting cli build, we get the following error

2024-08-06T19:00:32.095Z [WARNING]: ✖ There was an error initializing your environment.
2024-08-06T19:00:32.103Z [INFO]: 🛑 DataStore does not support 1 to 1 connection with both sides of connection as optional field: User.conversation
Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/

My guess is that it has something to do with the Datastore thing, but we do not use datastore and would opt to disable/remove it from our amplify project, but we do not know how to.

One work around was to reproduce the amplifyPush.sh script and remove the codegen related tasks and then run an amplify push -y as a build step. Is there any issues in doing it this way? Or is there any way to disable Datastore.

Expected behavior

amplify deployment succeeds

Reproduction steps

Not really much to share here

Project Identifier

Log output

2024-08-06T19:00:28.304Z [WARNING]: Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.

277

2024-08-06T19:00:31.094Z [WARNING]: Be careful when using @auth directives on a field in a root type. @auth directives on field definitions use the source object to perform authorization logic and the source will be an empty object for fields on root types. Static group authorization should perform as expected.

278

2024-08-06T19:00:32.095Z [WARNING]: ✖ There was an error initializing your environment.

279

2024-08-06T19:00:32.103Z [INFO]: 🛑 DataStore does not support 1 to 1 connection with both sides of connection as optional field: User.conversation

280

Learn more at: https://docs.amplify.aws/cli/project/troubleshooting/

281

2024-08-06T19:00:32.175Z [INFO]:

282

2024-08-06T19:00:32.176Z [INFO]: Session Identifier: 4716c47b-7212-482f-a684-678d3f19f461

283

2024-08-06T19:00:32.271Z [ERROR]: !!! Build failed

284

2024-08-06T19:00:32.271Z [ERROR]: !!! Error: Command failed with exit code 1

Additional information

No response

Before submitting, please confirm:

• I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.
• I have removed any sensitive information from my code snippets and submission.

[ykethan]

Hey,👋 thanks for raising this! I'm going to transfer this over to our API repository for better assistance 🙂

[chrisbonifacio]

Hi @gakinson , that is indeed a strange error to see if DataStore is not enabled.

Can you check your amplify/backend/api/<apiName>/cli-inputs.json file and let me know if there is a property like this?

"conflictResolution": {
  "defaultResolutionStrategy": {
    "type": "AUTOMERGE"
  }
},

If not, then I'm not sure why the hosting build would have it enabled. You then might want to check what version of the Amplify CLI the hosting build is using and make sure it matches the version you've upgraded to locally.

[gakinson]

Hello @chrisbonifacio,

This is our cli-inputs.json

What I noticed in the amplify docs is that it is initialized when the aws-amplify/datastore dependency is added to the project, which is there by default when you use the aws-amplify library which is required.

[chrisbonifacio]

Thank you for sharing @gakinson . An empty config means that DataStore is not enabled on your API. Were you able to check the Amplify CLI version that your hosting build is using?

Also, you mentioned removing "codegen related tasks" from the amplifyPush.sh script. Can you share what tasks exactly they were performing? Was there an amplify codegen models command being run?

[gakinson]

@chrisbonifacio This did not end up resolving the issue for me in the end. I still get the Datastore error on each build that has an API change. To make the deployment green, I just run it twice for now and the second build will succeed because it detects there are no changes to api and then it will not run the codegen commands.