- 
                Notifications
    You must be signed in to change notification settings 
- Fork 16
Parametrise target #10
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
| Sorrry I did something dumb - I opened up the original PR against main so now this is stacked on main w/ the changes from the other PR - I'll set this PR to draft for now. If the other ARM PR looks good then i'll update the base after merging it and then this will be ready for review. | 
| @ross-mcnairn-dev, merged your ARM branch. Thanks for that and sorry for the delay. | 
| 
 Hey, no worries at all! Happy to be able to make a small contribution here :). I'll clean this one up and open it tonight. | 
Merge pull request #9 from ross-mcnairn-dev/main
| OK, @JSv4 no rush on this, but this is ready for review when you've got a few this week | 
| Hey @JSv4 , do you think you'd have time to review this this week? | 
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.
Nice! Thanks for adding
| Thanks for the reminder @ross-mcnairn-dev | 
| This is great @ross-mcnairn-dev @JSv4 | 
In certain runtimes (AWS Lambda in my case), we are quite restricted on where we can write files. When we extract the compressed binaries and write them to the filesystem, they need to be written under
/tmpin Lambda, as that's the only writeable filesystem.So, here I'm parametrising the target path.