You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 9, 2024. It is now read-only.
I have my build to package individually and built using webpack. when doing a serverless deploy everything works fine, as it picks up the artifact needed to deploy via setting that's injected during the package phase, how ever. when running serverless deploy -p .serverless/
or
`serverless deploy --package .serverless/'
i get an error.
however doing serverless deploy -p .serverless/func1.zip
happly deploys func1 to ALL the functions, so func2 and 3 have func1 as there base encoded zip.
it seems that the --p and --package only support a single zip package deployment and does not cater for individually packaged deployments, as inspected in the deployFunction logic below
That's correct, right now that's not supported. At the moment, we don't have the bandwidth to work on this but we welcome any PR or contribution possible! Let me know if you can give this a try, I can help you with any issue you find.
I have my build to package individually and built using webpack. when doing a serverless deploy everything works fine, as it picks up the artifact needed to deploy via setting that's injected during the package phase, how ever. when running
serverless deploy -p .serverless/
or
`serverless deploy --package .serverless/'
i get an error.
however doing
serverless deploy -p .serverless/func1.zip
happly deploys func1 to ALL the functions, so func2 and 3 have func1 as there base encoded zip.
it seems that the --p and --package only support a single zip package deployment and does not cater for individually packaged deployments, as inspected in the deployFunction logic below
The text was updated successfully, but these errors were encountered: