Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Amplify push function does not push all files #13706

Closed
2 tasks done
kjsieffert opened this issue Apr 10, 2024 · 6 comments
Closed
2 tasks done

Amplify push function does not push all files #13706

kjsieffert opened this issue Apr 10, 2024 · 6 comments
Labels
functions Issues tied to the functions category pending-triage Issue is pending triage

Comments

@kjsieffert
Copy link

How did you install the Amplify CLI?

npm

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

16

Amplify CLI Version

12.10.1

What operating system are you using?

Linux

Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.

None

Describe the bug

After adding or updating files other than index.js (such as utility js files), running 'amplify push' does not deploy these file to the backend or recognize the files as having been changed. Note, I am using the Cloud9 editor.

Expected behavior

Any new file added to the lamda src directory or any modified existing file should be recognized and pushed when the function is deployed to the backend via an amplify push

Reproduction steps

Create a lambda function having an index.js file and a second file, like utility.js that is imported by the index.js file.
Deploy the new lambda function with 'amplify push'
modify the utility.js file in the editor (Cloud9)
run amplify status - it will incorrectly show nothing to update
run amplify push - it will incorrectly show nothing to push

please note - I am using the Cloud9 environment

Project Identifier

No response

Log output

# Put your logs below this line


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.
@kjsieffert kjsieffert added the pending-triage Issue is pending triage label Apr 10, 2024
@biller-aivy
Copy link

Try every time before you push, a amplify env checkout ...

This should be work

@kjsieffert
Copy link
Author

Ahh thank you. I will try this

@ykethan
Copy link
Member

ykethan commented Apr 12, 2024

@kjsieffert was not able to reproduce the issue locally, but as @biller-aivy suggested did the env checkout mitigate the issue?

@ykethan ykethan added functions Issues tied to the functions category pending-response Issue is pending response from the issue author labels Apr 12, 2024
@kjsieffert
Copy link
Author

@ykethan yes, thanks. I no longer see the issue after running an env checkout. This seems to get the front-end and backend back in sync. Thanks

@github-actions github-actions bot removed the pending-response Issue is pending response from the issue author label Apr 15, 2024
@ykethan
Copy link
Member

ykethan commented Apr 16, 2024

Glad to hear, thank you for the update.

@ykethan ykethan closed this as completed Apr 16, 2024
Copy link

This issue is now closed. Comments on closed issues are hard for our team to see.
If you need more assistance, please open a new issue that references this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
functions Issues tied to the functions category pending-triage Issue is pending triage
Projects
None yet
Development

No branches or pull requests

3 participants