-
Notifications
You must be signed in to change notification settings - Fork 5
fix(Invoke): Fixed Windows Issue by shipping pre-built binaries for platforms #51
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM overall, kudos for tackling this @Pive01 ! 🚀 Nice approach with using the CLI binaries directly, rather than spawning the separate container.
My only concern is around checking in the CLI binaries to this repo - they are fairly large, and it would be preferable to not have them in the repo imo (as we'll likely need to update them frequently over time). Could we download them from the Github releases page, or alternatively put them into an S3 bucket and download them when building the image? (i.e., in Dockerfile
)
Co-authored-by: Waldemar Hummer <waldemar.hummer@gmail.com>
Yes, I've added a little script that download and extract them when you build the extension 👍 |
This PR moves away from the logic we used until now: spawning a container and invoking the cli within the container. Now we ship all the binaries with the extension itself and invoke the correct ones based on the host OS/architecture. This is made to circumvent an issue we currently have on Windows machines where the path for the LOCALSTACK_VOLUME_DIR env variable was being mixed with Windows and Unix pathing.
/cc @alexrashed
Closes #52