-
Notifications
You must be signed in to change notification settings - Fork 825
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
Package update does not affect lambda layers in Windows 10 #13353
Comments
Hey @wrlakshan 👋 thanks for raising this! Lambda layer changes can be tricky with changing state on |
Hey @josefaidt |
Hey @wrlakshan thanks for clarifying! After updating a dependency in the layer can you run |
|
Hi @josefaidt I attempted to execute the command amplify env checkout prior to the push operation. However, it didn’t seem to make any difference. |
Hey @wrlakshan, the issue appears to be similar to bug on #10371 |
Hey @ykethan, I try this but it does not work. |
Possible workaround: from:
to:
|
Closing due to inactivity and in favor of tracking #10371 |
|
Amplify is looking in |
How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
v16.16.0
Amplify CLI Version
12.7.0
What operating system are you using?
Windows
Did you make any manual changes to the cloud resources managed by Amplify? Please describe the changes made.
No manual changes made
Describe the bug
when I change the package.json file dependencies in the lambda layer and push those changes the lambda layer does not update Even amplify does not recognize the layer is changed.Amplify
Expected behavior
lambda layer can be update in the windows
Reproduction steps
1.change the lambda layer dependecies.
2. push it
Project Identifier
No response
Log output
Additional information
No response
Before submitting, please confirm:
The text was updated successfully, but these errors were encountered: