Replies: 3 comments 2 replies
-
|
Thanks for starting this discussion. I’m currently on a trip, and I don’t have much time to look into this in detail. I think supporting several formats could make sense, it should also be easy to implement. Deploying a zip directly would require a little bit more work and changes. Currently, when you run the I’ll try to figure a solution when I’m back next week, but if you’d like to contribute, don’t hesitate to send PRs with some of this implemented. I always welcome those contributions. |
Beta Was this translation helpful? Give feedback.
-
|
Yes I might try for the multiple formats as the binary part looks difficult. I will have a look 😄 |
Beta Was this translation helpful? Give feedback.
-
|
I built the option of deploying the zip file directly in #800. I think it's what most people would expect. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks a lot! Amazing! ❤️ |
Beta Was this translation helpful? Give feedback.
-
|
Changed released in version 1.7.0 |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Let's say I have already run
cargo lambda build --output-format zipin a Docker container and saved this zip on my host system, as I only need it for my CDK. When I want to do a manual deployment withcargo lambda deploy, I encountered that it is currently not possible for me to use this zip directly, I need the binary (which is then zipped again). My current solution is to runoutput-format zipANDbinaryone after the other, but I wanted to ask if it is possible to use the zip file directly?Not necessarily related, but perhaps also an idea: allow multiple output formats:
cargo lambda build --output-format binary --output-format zipor (as it seems not practical to have anything else in the future:--output-format both(orall)Beta Was this translation helpful? Give feedback.
All reactions