feat: Use go build command instead of go run command
#1356
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks @uh-zz ! Note: tests are failing. |
|
@dherault |
dherault
approved these changes
Apr 18, 2022
|
thank you @uh-zz !! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
When launching Go's lambda, use
go buildcommand instead ofgo runcommand to run the binary file.Motivation and Context
I was looking for a way other than using
--useDockerbefore and came up with the following issue.#1334
Also, I found and commented on pull requests to add the feature to do local launches without
--useDocker#1320 (comment)
go buildcommand alows you to import and use all packages including main, so you can use not only a single main.go, but also separate packages.