josefaidt/amplify-cli-symlink-issue-workaround.md

Last active August 11, 2022 18:32

Star (0) You must be signed in to star a gist
Fork (0) You must be signed in to fork a gist

Learn more about clone URLs
Clone this repository at <script src="https://gist.github.com/josefaidt/a117076b7bea81e1872e275176dbb23c.js"></script>
Save josefaidt/a117076b7bea81e1872e275176dbb23c to your computer and use it in GitHub Desktop.

Amplify CLI symlink issue with functions

Raw

amplify-cli-symlink-issue-workaround.md

If you run into the following error there are two steps we can take to mitigate this error that do not involve modifying/replacing the #current-cloud-backend.zip archive in your deployment bucket.

🛑 An error occurred during the push operation: /
EEXIST: file already exists, symlink '../ulid/bin/cli.js' -> '/myproject/amplify/.temp/#current-cloud-backend/function/somelayer/lib/nodejs/node_modules/.bin/ulid'

In your file explorer perform the following:

delete the node_modules folder of the affected layer (using the example above, rm -rf amplify/#current-cloud-backend/function/somelayer/lib/nodejs/node_modules)
remove the .temp directory, rm -rf amplify/.temp

Once this is complete amplify push will successfully progress

Etep15 commented Aug 11, 2022

For anyone that runs into this issue but the above does not solve the problem. Using this in combination with this solution [amplify-graphql-syntax-workaround as per Josef's recommendation solved the problem for me. To make it clear, here are the steps I followed :

Login to AWS Web Console and go to S3
Select your deployment bucket (ie. amplify-[YOUR_PROJECT]-[YOUR_ENV]-[SOME #}-deployment)
download the #current-cloud-backend.zip file.
Set the directory to your root project folder (contains the amplify folder)
unzip this file by doing the following (dependant on where the zip file you downloaded is, I temporarily copied it to my project folder) unzip #current-cloud-backend.zip -d amplify/#current-cloud-backend
Remove the node_modules in your lambda layer in the #current-cloud-backend folder with rm -rf amplify/#current-cloud-backend/function/[YOUR_LAMBDA_LAYER_NAME]/lib/nodejs/node_modules
Remove the temp folder with rm -rf amplify/.temp
cd amplify/#current-cloud-backend/
zip -r "../#current-cloud-backend.zip" *
cd ..
Upload the new #current-cloud-backend.zip file to the S3 bucket (click the orange Upload button). This will overwrite the existing .zip file that is already there (the one your downloaded before).
cd .. You should now be back in the root folder of your project (where the amplify folder exists).
amplify push --force