Closed triptec closed 5 years ago
Hi @triptec thanks for reaching out. Do you have a concrete example of what you're blocked on. I can think of a few ideas. Atm this plugin only bundles your rust binary into a deployment. I could add a hook to also include other binaries. Alternatively there's a newer feature of lambda that serverless exposes called layers which may be of interest
Well, I've been playing around with crates that depend on sys crates and those sys crates depend on c headers and dynamic libraries. So my work flow right now is
Thanks posting back.
I think I have some idea for how to make this happen. I'll try to turn those ideas into code next weekend.
I think this the fact that this plugin leverages the actual lambda runtime makes binaries will be deployed into actually enables some predicability useful approaches.
I can get a list of provided libs in the runtime using
$ ldconfig -c -new -p
then in the lambda rust docker image I can get a list of link dependencies using
$ ldd {bin-name}
what I'd have to bundle into the zip is just whats missing from the runtime.
Yes that’s what I was playing with in my head as well. Though I think there would need to be a option like “include” or something that also would be added to the final zip. Like in my case there’s .gir files because of gobject-introspection though now that I think of it that might not be a dependency on those. I’ll have to look that up. Anyhow, thanks for taking the time making this, serverless and rust is neat on their own and even more together.
no doubt. thanks for reaching out. I'm always interested in seeing how people are using this
Hello, I’ve been playing around with this plugin and I wonder if you got any idea for how to handle dependencies on dynamic libs? Just add the lib folder if it exist to every binary zip or perhaps something else? I’d like to hear your thoughts on the matter. Thanks